icinga2-diagnostics
icinga2-diagnostics copied to clipboard
Icinga
Shell script for analyzing Icinga 2 installations.
Needs #6 to be implemented first
Check if the checks are evently distributred between nodes within an zone. When this new feature is implemented, we should collect some sample data from setups and then introduce thresholds...
We should check if something was changed in cleartext files. Namely Icinga Web code or Icinga Web modules. The first way that comes to mind is shipping Diagnostics with a...
Since Icinga 2 2.11 Hosts and Services defined in `conf.d` have no Zone and can't work as target for `command_endpoint`. ref/NC/702367 See https://community.icinga.com/t/checkable-with-command-endpoint-requires-a-zone-even-though-it-worked-in-2-10/2916 for details
While it's totally fine to have a mix of configuration from Director and DSL in some cases it's a source of potential errors. So we should report mixed configuration with...
Anywhere in the code the diag script calls `find` like this ` for i in $(find / -name php.ini 2>/dev/null)` Doing `find /....` without any excludes is IMHO a bad...
Logfiles piling up in `/var/lib/icinga2/api/log` are a clear indication of connection problems between nodes. We should check for their existence.
the icinga2 packages for debian-based distribution has missed, now added.
Agents should always have set `log_duration` in `endpoint` objects set to 0. They don't need a log especially when being `command_endpoint` and in fact it can be problematic. We need...