How to move the Kubernetes monitors from one Site24x7 account to another

How to migrate Kubernetes monitors from one Site24x7 account to another

Use case  

An existing Site24x7 user has Kubernetes monitoring in a Site24x7 account and plans to migrate his Kubernetes monitors to a different account.

The historic data and the current display name of the Kubernetes monitors will not be migrated. The Kubernetes monitor will be added as a new monitor under the new Site24x7 account and no past data will be available.

 

Solution  

In Site24x7, an account, irrespective of the number of Kubernetes monitors, will have only one device key mapped to it.

 

So, in order to change a Kubernetes agent to point to a particular Site24x7 user account, you have to make a few changes to the agent configuration.

 

You can locate the Device Key of your Site24x7 account by going to Admin > Developer > Device Key. Please make a note of the Device Key of the account to which the monitors are to be migrated.

 

Steps to be followed:  

  1. Download the site24x7-agent.yaml file and save it in your Cloud Terminal.

  2. Execute the below commands to migrate the Kubernetes monitors:

    kubectl delete secret site24x7-agent
    kubectl create secret generic site24x7-agent --from-literal KEY=<new_acc_device_key> && kubectl apply -f site24x7-agent.yaml

 

Once the mapping is complete, you can view the Kubernetes monitors from your new account. You can suspend or delete the Kubernetes monitors from the old account.

 

If you use a custom namespace, replace the namespace in the Site24x7 agent YAML file with your namespace.  

 

 

Customers also search for:

How to add Kubernetes currently monitored by Site24x7 in one account to a different Site24x7 account  

 

 


    • Related Articles

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

    • How does Site24x7 always ensure the availability of its location agents during monitoring?

      Site24x7 uses a preferred location recheck logic in the back-end to ensure the availability of all monitoring locations. This logic is only applied when you've disabled the option "Restrict monitoring within selected locations" in the Add or Edit ...

    • How to uninstall the Site24x7 Windows Server Monitoring Agent

      Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...

    • Monitors that require On-Premise Pollers in Site24x7

      Certain monitor types in Site24x7 require the use of On-Premise Pollers for data collection, especially when monitoring internal, firewall-restricted, or private resources. Depending on the type of monitoring, additional modules like the Network ...

    • What are Basic and Advanced Monitors?

      Site24x7 licensing and pricing work based on the monitor type categorization. For the ease of usage and based on the complexity of monitoring, we have categorized Site24x7 monitors as Basic Monitors and Advanced Monitors. We typically charge for a ...