Info |
---|
Sometimes, you may want to change a remote site to become |
...
Status |
---|
colour | Green |
---|
title | LAST TESTED ON CHECKMK 2.2.0P1 |
---|
|
Panel |
---|
borderColor | black |
---|
bgColor | #f8f8f8 |
---|
title | Table of Contents |
---|
|
|
Getting Started
Background information regarding this subject is available on our:
Step-by-step guide
- On the central site: Go to Setup → Distributed Monitoring -> → Edit the slave remote connection and deselect 'Disable configuration via WATO Setup on this site' (if selected)
Now your remote site has its own WATOconfiguration/wato.
Image Added
- Now you need to move all hosts from central to remote
On the central site: Go to WATO Setup -> Hosts and edit all hosts. You need to select 'Monitored on Site' for your remote site.
Please save and activate the changes.
Image Added
- You need to do a rediscovery for all hosts
- Now your remote site is monitoring all your hosts
- On the central site: Go to Distributed Monitoring and remove the remote Connection.
- Please Note: If
On the remote site: Go to Distributed Monitoring and add create a connection for the central site.
Note |
---|
If you enable 'configuration push,' the remote site will override the central site. Please ensure you have all rules/settings already on your remote site. |
- After activating all changes, the central site is not monitoring any host. Please repeat step 2 if you want to monitor the host via central.
- Now you've successfully promoted remote to central.
...
Filter by label (Content by label) |
---|
showLabels | false |
---|
max | 5 |
---|
spaces | KB |
---|
showSpace | false |
---|
sort | modified |
---|
reverse | true |
---|
type | page |
---|
cql | label in ( "distributed_monitoring", "slave_to_master" , "distributed" ) and type = "page" and space = "KB" |
---|
labels | distributed_monitoring slave_to_master |
---|
|
...