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.
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
xyz
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 Downloaded agent has size 13111604 bytes. Signature check OK. Invoking package manager: dpkg -i /tmp/check-mk-agent-tq29w24g Output from dpkg: (Reading database ... 158559 files and directories currently installed.) Preparing to unpack /tmp/check-mk-agent-tq29w24g ... Disable Checkmk agent in systemd (if active)... Unpacking check-mk-agent (2.0.0b4-20.67f84ee7e41b73aa) over (2.0.0b4-20.67f84ee7e41b73aa) ... Reloading xinetd... Setting up check-mk-agent (2.0.0b4-20.67f84ee7e41b73aa) ... Reloading xinetd... Enable Checkmk agent in systemd... Created symlink /etc/systemd/system/sockets.target.wants/check-mk-agent.socket → /etc/systemd/system/check-mk-agent.socket. Successfully installed agent 67f84ee7e41b73aa. root@ip-172-31-34-134:/home/ubuntu#
- Setup → General → Global settings → AUTOMATIC AGENT UPDATES → Connection to the central agent bakery
Related articles
Filter by label
There are no items with the selected labels at this time.