Host state differs between Icinga2 API and host_state table in database

[moreamazingnick]

This user had a very similar problem:

@vutuong

I noticed that the last_update time is much older compared to the time shown on the web interface. Why is this happening?

@moreamazingnick

the reason for this is, that the most recent non hard state change information is stored in the redis server only.

The sql database hold the hard state relevant for “reboot consistant” sla calculation.

It is quite easy to implement something like this query in php as an icingaweb2 module.
Inside icingeweb2 you can easyily combine the redis data with the sql data.

• Icinga2 API has has the most current information about the icinga objects.
• The most recent check-result and last_update are stored in redis
• If there is a state change, in order to do SLA calculations later, there is an update on the relational mariadb/mysql//postgres database.
• A restart of Icingadb.service or the icinga2.service will trigger an update on the relational database.

https://icinga.com/docs/icinga-2/latest/doc/14-features/#icinga-db

Icinga DB is a set of components for publishing, synchronizing and visualizing monitoring data in the Icinga ecosystem, consisting of:

• Icinga 2 with its icingadb feature enabled, responsible for publishing monitoring data to a Redis server, i.e. configuration and its runtime updates, check results, state changes, downtimes, acknowledgements, notifications, and other events such as flapping
• The Icinga DB daemon, which synchronizes the data between the Redis server and a database
• And Icinga Web with the Icinga DB Web module enabled, which connects to both Redis and the database to display and work with the most up-to-date data