Uploaded image for project: 'Managed Service - Streams'
  1. Managed Service - Streams
  2. MGDSTRM-8454

Create unit tests for remaining container down & Prometheus volume filling up alerts

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • MK - Sprint 219

      WHAT

      Create a  unit test for the 

      This Jira contains sub-tasks for the creation of a unit test for the following critical alert in the  observability-resources-mk repository:

      • ObservabilityOperatorPrometheusPersistentVolumeFillingUp
      • OpenshiftMonitoringFederationScrapeTargetDown
      • KasFleetShardOperatorContainerDown
      • KasFleetShardSyncScrapeTargetDown

      HOW:

      The alerts should be tested for firing and non-firing scenarios as well as close to value boundaries if possible.

      DONE:

      A unit test is considered done when each alert has been tested for the following scenarios:

      1. A scenario where the test doesn't make the alert fire

      2. A scenario where the test does make the alert fire

      Guidelines

      The following steps should be adhered to:

        • Required tests should be put in place - unit, integration, manual test cases (if necessary)
        • CI and all relevant tests passing
        • Changes have been verified by one additional reviewer against:
        • each required environment
        • each supported upgrade path
        • If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged

            ihutchin@redhat.com Ian Hutchinson (Inactive)
            ihutchin@redhat.com Ian Hutchinson (Inactive)
            MK - Running the Service
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: