It is now possible to deploy Deploying baked agents via remote sites within a distributed monitoring configuration is now possible.
| Table of Contents |
|---|
Prerequisites
Prerequisites for this feature are a monitoring setup using distributed WATO and the possibility to establish of establishing a connection from remote sites to the central site via HTTP/HTTPS.
Also, you need to configure the distributed agent bakery.
...
With Checkmk 2.0, there is a new option for the Agent Updater:
Usage: In the case of "Registration and fallback," , the agent updater will use this information only on registration and rely on the update URL provided by the agent bakery afterwardsafterward. If the connection fails, the agent updater will additionally use this information as a fallback. In the case of "Use for all connections," , the agent updater will ignore the update URL provided by the agent bakery.
If you want to register und and update all remote hosts from a remote site, now you can add the slave site here:
...
If you want to run the agent updater, this will not work.
| Code Block |
|---|
root@ip-172-31-40-133:/home/ubuntu# cmk-update-agent -v +-------------------------------------------------------------------+ | | | Check_MK Agent Updater v2.0.0b5 - Update | | | +-------------------------------------------------------------------+ Getting target agent configuration for host 'slave1' from deployment server Agent Bakery: Registering/updating at remote site but found no URL to central site. Please provide it in "automatic agent updates" section at global settings. See syslog or Logfile at /var/lib/check_mk_agent/cmk-update-agent.log for details. |
...
To get the updater working, please follow the Stepstep-by-step guide!
Step-by-step guide
...
| Info |
|---|
In 'Setup → General → Global settings → AUTOMATIC AGENT UPDATES' there is a second new option for the distributed agent bakery:
Configure an alternative URL for the connection from the host to remote agent bakery. If not configured here, the URL from distributed monitoring configuration is used instead. In many cases, you You might often want to make this a site-specific global setting at the distributed monitoring configuration , because this URL is likely different for every remote site. |
...
This feature is realized as follows: Update requests to the remote sites get forwarded to the central site – The entire configuration and the agent baking process is are done on the central site. Agent packages that got requested once at a remote site will get cached (as long as they are valid) there to save unnecessary traffic. Additionally, the requested data will be checked for consistency on the remote site, again to save unnecessary traffic to the central site.
...
The agent updater creates a config and a state file. Please dont don't modify this file! You can take a look inside to see if the config is correct!
...