Ansible/roles/checkmk_configure_agent/README.md

checkmk_configure_agent

On Windows, AIM owns only the top-level plugins: section of check_mk.user.yml. The role preserves all other top-level sections and comments, including global, winperf, fileinfo, logwatch, local, and mrpe.

The first line is an AIM ownership notice. The managed plugins: section also gets its own ownership comment so operators can see the exact management boundary.

Operator defaults are intentionally low-precedence; inventory and explicit run options may override them.

---
checkmk_windows_user_cfg: C:\ProgramData\checkmk\agent\check_mk.user.yml
checkmk_windows_updates_timeout: 3600
checkmk_windows_updates_cache: 43200
checkmk_mk_inventory_timeout: 120
checkmk_plugins_default_timeout: 120
checkmk_plugins_default_cache: 600
checkmk_extra_plugin_patterns: []

checkmk_extra_plugin_patterns entries are inserted before AIM's standard plugin rules. AIM does not manage local: or mrpe: from this role; existing host-specific configuration in those sections is left intact.

Structured result integration

Current reporting behavior and field semantics are specified in scripts/docs/OPERATION_RESULTS.md. The calling catalog playbook owns publication; helper roles do not implicitly export arbitrary facts, module results or debug data. Existing defaults above retain their precedence. See the current validation/sanity documents before using the new candidate.