Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3831

[release-5.7] Default configuration is not restored under loki config after RulerConfig deletion

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • OBSDA-115 - Create alerting rules based on logs
    • VERIFIED
    • Hide
      Before this update, when the RulerConfig is deleted, the operator does not update the Loki configuration. With this update, deleting RulerConfig updates the LokiStack annotations which results in updating the Loki configurations.
      Show
      Before this update, when the RulerConfig is deleted, the operator does not update the Loki configuration. With this update, deleting RulerConfig updates the LokiStack annotations which results in updating the Loki configurations.
    • Log Storage - Sprint 234

    Description

      Deleting the RulerConfig CR does not default back ruler configuration under loki config. Ruler restart does not take place after deletion.

      $ oc get RulerConfig -n openshift-logging
      No resources found in openshift-logging namespace.
      $oc get cm/lokistack-dev-config -n openshift-logging
      runtime-config.yaml (overrides) after deletion
      overrides:
        application:
          ruler_alertmanager_config:
            alertmanager_url: https://_web._tcp.alertmanager-operated.openshift-user-workload-monitoring.svc
            enable_alertmanager_v2: true
            enable_alertmanager_discovery: true
            alertmanager_refresh_interval: 1m
            alertmanager_client:
              tls_ca_path: /var/run/ca/alertmanager/service-ca.crt
              tls_server_name: alertmanager-user-workload.openshift-user-workload-monitoring.svc.cluster.local
              type: Bearer
              credentials_file: /var/run/secrets/kubernetes.io/serviceaccount/token
            alert_relabel_configs:
            -
              source_labels: ["severity","project"]
              regex: warning;my-app-1
              action: replace
              separator: ;
              replacement: uwmlogs
              target_label: project
      config.yaml after deletion
      ruler:
        enable_api: true
        enable_sharding: true
        evaluation_interval: 1m
        poll_interval: 1m
        external_labels:
          environment: prod
          region: us-east-1
        .....
      

      Version:
      OCP: 4.13
      Logging: 5.7.0

        Steps to Reproduce:
        1) Deploy CLO and LO
        2) Forward logs to Loki
        3) Enable user-workload-monitoring
        4) Create alerting and recording rules for app tenant
        5) Check default config
        6) Create RulerConfig
        7) Check config with updates as per RulerConfig
        8) Delete RulerConfig
        9) Validate config for defaults

      RulerConfig  CR: http://pastebin.test.redhat.com/1095410

      Expected Result: Defaults config should be applied once RulerConfig is deleted

      Actual Result: Defaults are not restored after deletion

      Attachments

        Activity

          People

            rh-ee-mbouqsim Mohamed-Amine Bouqsimi (Inactive)
            rhn-support-kbharti Kabir Bharti
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: