Page Comparison

...

Configure the connection to the central Agent Bakery

1. Setup → General → Global settings → AUTOMATIC AGENT UPDATES → Connection to the central agent bakery
   Image Modified
   
   
   Place checks on both URL to central site & Automation User for connection to central site. Fill in the information for the appropriate URL.
   Image Modified
   
   
   

2. Now you can update the host.

   Code Block
   language bash theme RDark
   root@linux:~# cmk-update-agent -v +-------------------------------------------------------------------+ | | | Check_MK Agent Updater v2.0.0b5 - Update | | | +-------------------------------------------------------------------+ Getting target agent configuration for host 'myremotesite' from deployment server Target state (from deployment server): Agent Available: True Signatures: 1 Target Hash: 1ef2302ca00a9b89 Agent 1ef2302ca00a9b89 already installed.

   
   
   

3. In 'Setup → General → Global settings → AUTOMATIC AGENT UPDATES' there is now a new second option for the distributed Agent Bakery:

   Image Modified

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

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

...

Possible Solution

Please make you followed follow the steps to import the SSL Certificates:

...