-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
Logging 5.5.0
-
False
-
None
-
False
-
NEW
-
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
-
VERIFIED
Created an alerting rule and recording rule for tenant: application but do not see details in loki ruler configmap.
tenant: infrastructure data is visible.
Steps to reproduce:
1) Install Loki operator
[kbharti@cube ~]$ oc get csv
NAME DISPLAY VERSION REPLACES PHASE
clusterlogging.v5.5.0 Red Hat OpenShift Logging 5.5.0 Succeeded
loki-operator.v5.5.0 Loki Operator 5.5.0 Succeeded
2) Create bucket secret and provision LokiStack CR
apiVersion: loki.grafana.com/v1beta1 kind: LokiStack metadata: name: lokistack-dev namespace: openshift-logging spec: size: 1x.small storage: secret: name: test type: s3 storageClassName: gp2 tenants: mode: openshift-logging rules: enabled: true selector: matchLabels: openshift.io/cluster-monitoring: "true" namespaceSelector: matchLabels: openshift.io/cluster-monitoring: "true"
[kbharti@cube ~]$ oc get pods | grep ruler lokistack-dev-ruler-0 1/1 Running 0 179m lokistack-dev-ruler-1 1/1 Running 0 3h5m
3) Create application and infrastructure alerting and recording rules.
4) Validate Loki ruler configmap for data.
Expected: Infra and application tenant alerting and recording are present in ruler config.
Actual: Only Infra tenant rules are present.