-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
-
-
Moderate
DESCRIPTION
When describing how to configure the Lokistack Ruler [0], in the example:
apiVersion: loki.grafana.com/v1
kind: LokiStack
metadata:
name: <name>
namespace: <namespace>
spec:
# ...
rules:
enabled: true [1]
selector:
matchLabels:
openshift.io/<label_name>: "true" [2]
namespaceSelector:
matchLabels:
openshift.io/<label_name>: "true" [3]
[1] Enable Loki alerting and recording rules in your cluster.
[2] Add a custom label that can be added to namespaces where you want to enable the use of logging alerts and metrics.
[3] Add a custom label that can be added to namespaces where you want to enable the use of logging alerts and metrics.
The points 2 and 3 are described as the same being this information not correct. As per Upstream documentation [1]:
- selector: A selector to select which LokiRules to mount for loading alerting/recording rules from.
- namespaceSelector: Namespaces to be selected for PrometheusRules discovery. If unspecified, only the same namespace as the LokiStack object is in is used.
[0][ https://docs.openshift.com/container-platform/4.16/observability/logging/logging_alerts/custom-logging-alerts.html#configuring-logging-loki-ruler_custom-logging-alerts|https://docs.openshift.com/container-platform/4.16/observability/logging/logging_alerts/custom-logging-alerts.html#configuring-logging-loki-ruler_custom-logging-alerts]
[1] https://loki-operator.dev/docs/api.md/#loki-grafana-com-v1-RulesSpec
