mirror of
https://github.com/Icinga/icingadb.git
synced 2026-06-11 01:40:57 -04:00
Icinga DB - Backend moderne
6068ab78d0
This improves the resulting sort order when `ORDER BY event_time, event_type` is used. `state_change` comes first as it can cause many of the other events like trigger downtimes, remove acknowledgements and send notifications. Similarly, `notification` comes last as any other event can result in a notification. This will result in history events for scenarios like state changes, triggers downtime, sends downtime start notification being sorted in that order. Apart from that, end events sort before the corresponding start events as any ack/comment/downtime/flapping period should last for more than a millisecond, therefore if there should be two events within the same millisecond, the end event corresponds to the older period and is sorted first. |
||
|---|---|---|
| .github | ||
| cmd | ||
| doc | ||
| internal | ||
| pkg | ||
| schema | ||
| tests | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| AUTHORS | ||
| CHANGELOG.md | ||
| config.example.yml | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| README.md | ||
Icinga DB
Icinga DB is a set of components for publishing, synchronizing and visualizing monitoring data in the Icinga ecosystem, consisting of:
- The Icinga DB daemon, which synchronizes monitoring data between a Redis server and a database
- Icinga 2 with its Icinga DB feature enabled, responsible for publishing the data to the Redis server, i.e. configuration and its runtime updates, check results, state changes, downtimes, acknowledgements, notifications, and other events such as flapping
- 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
Documentation
Icinga DB documentation is available at icinga.com/docs.
License
Icinga DB and the Icinga DB documentation are licensed under the terms of the GNU General Public License Version 2.