Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring rule updates are not synchronized to slave sites #44

Open
ganto opened this issue Jan 28, 2017 · 0 comments
Open

Monitoring rule updates are not synchronized to slave sites #44

ganto opened this issue Jan 28, 2017 · 0 comments
Labels
Milestone

Comments

@ganto
Copy link
Member

ganto commented Jan 28, 2017

When adding new rules to e.g. checkmk_server__site_cfg_rules they are properly configured for a master site, but if it has some slave sites they won't be automatically synchronized to the slave sites. The same issue exists for all site configurations done to a distributed setup by this Ansible role.

The problem is, that Check_MK itself doesn't know about the updated rules and therefore won't trigger its built-in synchronization mechanism. Unfortunately there is no API call which can trigger this synchronization. A possible solution for this issue is to create an Ansible task which would rsync the rule configuration files (e.g. rules.mk) to the appropriate slave sites. However, there are currently not enough information available to the master server on how to reach a slave server via Ansible.

Work-around: After updating the monitoring rules via Ansible, login to WATO, click edit on a monitoring rule, save it without modification and then apply the change. This will push the master site configuration to all slave sites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant