Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-2383

Onboard PSI OpenShift Onto Observatorium

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • None
    • RHOBS
    • Onboard psiocp into RHOBS
    • True
    • Hide
      This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic. If you believe this occurred in error, please reach out to the functional team for help in getting this work into their queue.
      Show
      This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic. If you believe this occurred in error, please reach out to the functional team for help in getting this work into their queue.
    • False
    • Not Selected
    • NEW
    • To Do
    • Impediment
    • NEW
    • 100
    • 100% 100%
    • 0

      Goal

      • To have the PSI OpenShift clusters send metrics to be stored in Observatorium for SLI/ SLO based monitoring from the metrics. 

      Acceptance Criteria

      • Need to see uninterrupted flow of metrics from our clusters over a period, say 7 days or so.

      Dependencies (internal and external)

      1. PSI clusters need to be functional at the time of metric forwarding

       

      Description of your servicePSI <> RHOBS meeting notes

      Explanation of why you need would benefit from sending data to Observatorium: Our team needs long-term storage of data (preferably 30 days) for importing on grafana.stage.engineering.redhat.com and grafana.engineering.redhat.com for dashboarding and alerting purposes. Our senior management decides on budgeting and proactive measures to take, to avoid outages based on the dashboard.

      All of the answers to the collected requirements from section 1:

      • What resources need to be collected? Logs? Metrics? Both?
      • What volume of data will be collected? XGb of logs per day? Xk metrics time series per day?
      • What is the expected or forecasted growth in collected data? X% growth in data per month?
      • How many users will require read access? X team members? The entire OpenShift org?
      • How many clients will be emitting data? 1 Prometheus server?
      • How long should data be retained? 2 weeks?
      • How many independent service accounts do you need to write data into the platform?

      The organization ID of the new customer portal account from section 2:
      A link to the Service Now ticket from section 3: https://redhat.service-now.com/surl.do?n=TASK1201377
      The email address specified in the service account in section 3: psi-openshift-admins@redhat.com

        1.
        PX Tracker Sub-task Closed Undefined Unassigned
        2.
        Docs Tracker Sub-task Closed Undefined Unassigned
        3.
        QE Tracker Sub-task Closed Undefined Unassigned
        4.
        TE Tracker Sub-task Closed Undefined Unassigned

            jlins@redhat.com Jéssica Lins (Inactive)
            pntdevops-kfryklun Keith Fryklund
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: