Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-42693

Fix SRE Checkpoint issues for consoleDot Cloud-Connector

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • None

      https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/cloud-connector/app.yml

      Checks:

      •  Service Owners. (there are 1 mailing list, 3 user emails, the service should has only mailing lists as serviceOwners and each entry is still valid.)
      •  escalationPolicy: https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/teams/insights/escalation-policies/crc-cloud-connector-escalations.yml description need cleanup, crc-pipeline-team or crc-remediations-team?
      •  SLOs documented as slo-document-1.yml files. (API request latency says 250ms, but prometheus record and alerts are 10ms. 
        Kafka Message processing latency says 500ms, but prometheus records and alerts are 1 second)
      •  Base functionality SOP. (base functionality: there is a documented SOP (within sopsUrl) to run a smoke test to determine basic functionality, so as an AppSRE we can check if the service is running correctly. For example in the case of quay.io we could test it with docker push/pull and by logging to the quay.io UI.)

              Unassigned Unassigned
              rh-ee-dwan Di Wang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: