upstream/icinga2
1
0
Fork 0
mirror of https://github.com/Icinga/icinga2.git synced 2026-06-09 00:32:12 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #10683 from Icinga/docs-10-itl-icingadb-explain

Browse source 
doc: Explain icingadb built-in check
This commit is contained in:
Alvar 2026-02-05 07:40:33 +00:00 committed by GitHub
commit 303b46bf14
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/10-icinga-template-library.md
View file

@ -108,6 +108,16 @@ cluster\_lag\_critical | **Optional.** Critical threshold for log lag in seconds
### icingadb <a id="itl-icinga-icingadb"></a>
Check command for the built-in `icingadb` check.
It performs multiple checks, such as verifying that:
- The `IcingaDB` object has an active Redis connection.
- The Icinga DB daemon is active and has recently sent a heartbeat to Redis.
- Exactly one Icinga DB daemon is claiming responsibility in HA mode.
- Icinga 2 does not take too long dumping the configuration to Redis (_full dump_).
- The Icinga DB daemon does not take too long synchronizing the configuration to the relational database (_full sync_).
- Icinga 2 does not generate more entires than it can write into the Redis queue (_redis backlog_).
- Icinga DB does keep up with reading entries from the Redis queue and writing it to the relational database (_database backlog_).
This might result in outdated history entries and object attributes, used for filtering by Icinga DB Web.
Custom variables passed as [command parameters](03-monitoring-basics.md#command-passing-parameters):