Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-7709

Monitoring of RHODS components

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Monitoring
    • False
    • None
    • False
    • Testable
    • No
    • No
    • No
    • Pending
    • None

      Monitoring RHODS components is essential for:

      • Easier support from MTSRE
      • Visibility on SLA/SLO for RHODS

      Keeping those goals in mind, we mostly need metrics about availability and performance of each RHODS components.

      Requirements:

      • the monitoring is adaptable to the addon flow and the self-managed flow
      • we can federate metrics across RHODS installation by storing them in a remote store (RHOBS or other), to give access to metrics without access to customer clusters
      • use standard components, in particular for all the RHODS operator based on operator-sdk, which already provides standard metrics. (https://book.kubebuilder.io/reference/metrics-reference.html)

            rh-ee-magautie Max Gautier (Inactive)
            rh-ee-magautie Max Gautier (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: