upstream/icingadb
1
0
Fork 0
mirror of https://github.com/Icinga/icingadb.git synced 2026-02-03 20:40:34 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

doc: Update for Notifications

Browse source 
Remove the generic information from 01-About.md and add a warning to
03-Configuration.md that this feature might not be stable.
This commit is contained in:
Alvar Penning 2025-11-11 15:08:15 +01:00
parent f8c2ab4b17
commit e8c0359c4e
No known key found for this signature in database
2 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/01-About.md
View file

@ -34,10 +34,6 @@ Icinga DB Web also connects to the Icinga 2 API with its Command Transport to ac
These are the components of Icinga DB embedded into an Icinga setup with Icinga 2 and Icinga Web 2.
Since the Icinga DB daemon always receives the latest information from Redis®, it is an ideal candidate to distribute information further.
In addition to inserting data into a relational database, Icinga DB can also forward events to [Icinga Notifications](https://icinga.com/docs/icinga-notifications/),
as described in the [configuration section](03-Configuration.md#notifications-source-configuration).
## Installation
To install Icinga DB see [Installation](02-Installation.md).

6
doc/03-Configuration.md
View file

@ -176,6 +176,12 @@ ICINGADB_RETENTION_OPTIONS=comment:356
## Notifications Source Configuration
!!! warning
The Icinga Notifications integration is a feature preview that you can try out.
However, incompatible changes may happen, so be sure to check the changelog for future updates.
Please do not use it in production.
Icinga DB can act as an event source for [Icinga Notifications](https://icinga.com/docs/icinga-notifications/).
If configured, Icinga DB will submit events to the Icinga Notifications API.