-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Logging 5.8
-
13
-
False
-
-
False
-
-
-
OBSDOCS (Jan 22 - Feb 12) #248
-
Important
The Creating a log-based alerting rule with Loki is very limited and missing many details to actually understand how to create AlertingRule rules and then manage the same.
While the example Example infrastructure AlertingRule CR is kind of OK, the example Example application AlertingRule CR is definitely unclear.
Here it's highlighted that a user specific namespace can be used. But it's missing out what permissions are required (see OBSDOCS-781) and even more important how to use the feature when user workload monitoring is enabled and running on the OpenShift Container Platform 4 - Cluster. Hence it's not clear how/where Alerts are being routed and how to configure a specific Alertmanager to push the alerts to the respective application team.
This section therefore needs to be enhanced massively to show how alerting can/should be configured for platform but also user application, when user workload monitoring is enabled or disabled (both cases should be documented).
Further, the documentation is also missing information/details about RecordingRules, what it is, how to use it, etc. and the same applies to RulerConfigs. This should also be added with a potential example to help customers understand what those resources are about and how to use them.
- is related to
-
OBSDOCS-781 Authorizing Loki rules RBAC permissions for Custom logging alerts is unclear
- Closed