It is now possible to deploy baked agents via remote sites within a distributed monitoring configuration.
Prerequisites
Prerequisites for this feature are a monitoring setup using distributed WATO and the possibility to establish a connection from remote sites to the central site via HTTP/HTTPS.
Also you need to configure the distributed agent bakery.
Step-by-step guide
- Configure the connection to the central agent bakery
Setup → General → Global settings → AUTOMATIC AGENT UPDATES → Connection to the central agent bakery
Now you can register and update the host
root@ip-172-31-34-134:/home/ubuntu# cmk-update-agent register -v +-------------------------------------------------------------------+ | | | Check_MK Agent Updater v2.0.0b4 - Registration | | | | Activation of automatic agent updates. Your first step is to | | register this host at your deployment server for agent updates. | | For this step you need an administration account on WATO for | | that server. | | | +-------------------------------------------------------------------+ Using previous settings from /etc/cmk-update-agent.state. Password for user 'cmkadmin': Going to register agent at deployment server Successfully registered agent of host "slave2" for deployment. You can now update your agent by running 'cmk-update-agent -v' Saved your registration settings to /etc/cmk-update-agent.state. root@ip-172-31-34-134:/home/ubuntu# cmk-update-agent -v +-------------------------------------------------------------------+ | | | Check_MK Agent Updater v2.0.0b4 - Update | | | +-------------------------------------------------------------------+ Getting target agent configuration for host 'slave2' from deployment server Target state (from deployment server): Agent Available: True Signatures: 1 Target Hash: 67f84ee7e41b73aa Agent 67f84ee7e41b73aa already installed. root@ip-172-31-34-134:/home/ubuntu#
Related articles
Filter by label
There are no items with the selected labels at this time.