mirror of
https://github.com/Icinga/icingadb.git
synced 2026-02-19 02:28:28 -05:00
Icinga DB - Backend moderne
697eca139d
- Bump IGL to latest changes in Icinga/icinga-go-library#145. - Allow specifying which pipeline keys are relevant, ignore others. - Allow specifying which pipeline key should be parsed in which type. - Create history.DowntimeHistoryMeta as a chimera combining history.DowntimeHistory and history.HistoryDowntime to allow access event_type, distinguishing between downtime_start and downtime_end. - Trace times for submission steps in the worker. Turns out, the single threaded worker blocks roughly two seconds for each Client.ProcessEvent method call. This might sum up to minutes if lots of events are processed at once. My current theory is that the delay results in the expensive bcrypt hash comparison on Notifications. |
||
|---|---|---|
| .github | ||
| cmd | ||
| doc | ||
| internal | ||
| pkg | ||
| schema | ||
| tests | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| .mailmap | ||
| AUTHORS | ||
| CHANGELOG.md | ||
| config.example.yml | ||
| Containerfile | ||
| 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.