Bug 54749 - Add LDAP schema and UDM modules for monitoring via Prometheus alertmanager
Add LDAP schema and UDM modules for monitoring via Prometheus alertmanager
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Monitoring (Prometheus or Nagios)
UCS 5.0
Other Linux
: P5 normal (vote)
: UCS 5.0-2
Assigned To: Florian Best
Siavash Sefid Rodi
:
Depends on:
Blocks: 54904
  Show dependency treegraph
 
Reported: 2022-05-12 17:12 CEST by Florian Best
Modified: 2022-07-04 14:08 CEST (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2022-05-12 17:12:19 CEST
We should create LDAP schemata and UDM modules for the new alerting via Prometheus / Grafana.

It's not yet decided if we will use Prometheus AlertManager or Grafana builtin alerts but they provide the same functionality.

There are:
* Recoding rules (checks)
→ name, metric / query, summary, description, labels, (... conditions, no-data, error handling)

* Contact points
→ name, type (email, sms, Telegram, webhook, …), type-specific settings e.g. address/credentials/etc., message, notification settting: disabled resolved message

* Silences
→ (name), start-time + end-time / duration, labels, comment (description)

- [ ] add LDAP schema for new alerting objects
- [ ] add UDM modules (e.g. monitoring/*) for new alerting objects
- [ ] add a migration script which transforms Nagios checks into Alerting rules and maybe other Nagios setttings
- [ ] add extended attribute for computer objects to assign checks (TBD: store the checks at the computer or at the rule?)
Comment 1 Florian Best univentionstaff 2022-05-23 14:28:28 CEST
* Alert group
→ name
Comment 3 Florian Best univentionstaff 2022-06-23 19:19:50 CEST
univention-updater (15.0.4-1)
6fc0d08d2142 | Bug #54749: migrate nagios systems to alerts

univention-monitoring-client (1.0.0-1)
3ddadc0ff876 | Bug #54749: Add UMC integration for monitoring alerts
6fc0d08d2142 | Bug #54749: migrate nagios systems to alerts
aa3c8119a560 | Bug #54749: auto assign all checks
5208f5434922 | Bug #54749: add UDM module monitoring/alert

univention-management-console-module-udm (10.0.2-2)
3ddadc0ff876 | Bug #54749: Add UMC integration for monitoring alerts

changelog-5.0-2.xml
ea32350e969f | Changelog Bug #54748 Bug #54749 Bug #54750
Comment 4 Siavash Sefid Rodi univentionstaff 2022-06-28 10:48:54 CEST
OK : * Recoding rules (checks) → name, metric / query, summary, description, labels, (... conditions, no-data, error handling)

OK, only e-mail implemented: * Contact points → name, type (email, sms, Telegram, webhook, …), type-specific settings e.g. address/credentials/etc., message, notification settting: disabled resolved message

Not implemented, may be done in the future: * Silences → (name), start-time + end-time / duration, labels, comment (description)

[X] add LDAP schema for new alerting objects
[X] add UDM modules (e.g. monitoring/*) for new alerting objects
[X] add a migration script which transforms Nagios checks into Alerting rules and maybe other Nagios setttings
[X] add extended attribute for computer objects to assign checks (TBD: store the checks at the computer or at the rule?)
Comment 5 Florian Best univentionstaff 2022-07-04 14:08:17 CEST
UCS 5.0-2 has been released.

https://docs.software-univention.de/release-notes-5.0-2-en.html

If this error occurs again, please clone this bug.