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:
Download the site24x7-agent.yaml file and save it in your Cloud Terminal.
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, ...Exclude Site24x7 monitoring traffic from Google Analytics
You can exclude traffic from the Site24x7 Web Transaction (Browser) monitor and Webpage Speed (Browser) traffic from Google Analytics in two ways. To exclude traffic for the Web Defacement monitor, you can follow the first method. 1. Creating a ...Response time in Website monitoring
In website monitoring, response time is calculated as the total time taken to resolve the DNS, complete the TCP hand-shake, negotiate an SSL handshake (for HTTPS) and download the full HTML output from the server. However, it does not include getting ...Compare our various methodologies for Website Monitoring
Get to know Site24x7 monitors better and choose the one that best fits your monitoring needs. Compare the functionality of the following monitors: Website Monitoring Webpage Speed (Browser) Web Transaction Monitoring Web Transaction (Browser) SSL/TLS ...Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring
By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...