Versions Compared

Version Old Version 15 New Version 16
Changes made by

Anastasios Thomaidis

Anastasios Thomaidis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Configure the connection to the central agent bakery

    1. Setup → General → Global settings → AUTOMATIC AGENT UPDATES → Connection to the central agent bakery

      Info


    2. Now you can register and update the host

      Code Block
      root@ip-172-31-40-131:/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-40-131:/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-40-131:/home/ubuntu#


Info

In 'Setup → General → Global settings → AUTOMATIC AGENT UPDATES' there is a second new option for the distributed agent bakery:

Image Added

Configure an alternative URL for the connection from host to remote agent bakery. If not configured here, the URL from distributed monitoring configuration is used instead. In many cases, you might want to make this a site specific global setting at the distributed monitoring configuration, because this URL is likely different for every remote site.


Functionality


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 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.

...