Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-2647

Add/expose metrics of Machine-Config-Operator (MCO)

    XMLWordPrintable

Details

    • False
    • False
    • OCPSTRAT-554 - Improving error handling, propagation, collection, and disambiguation for users
    • 0
    • 0% 0%

    Description

      1. Proposed title of this feature request
           Add/expose metrics in Prometheus for MachineConfigOperator.
              
      2. What is the nature and description of the request?
           Customer like to have in Prometheus some metrics of MachineConfigOperator. For each MCP:
          
          - Paused
          - Updated
          - Updading
          - Degraded
          - Machinecount
          - ReadyMachineCount
          - UpdatedMachineCount
          - DegradedMachineCount
         

      3. Why does the customer need this? (List the business requirements here)
           These metrics would be really important, as it could show any MachineConfig action (updating, degraded, ...), which could also even trigger an alarm with a PrometheusRule. Having a dashboard of MachineConfig would be also really useful.

      4. List any affected packages or components.

         MCO and Monitoring

      Attachments

        Issue Links

          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MCO-1 Observability Infrastructure and Enhanced metrics in MCO

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-554 Improving error handling, propagation, collection, and disambiguation for users

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • In Progress

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-844 Expose additional MCO metrics in Prometheus

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              rhn-support-mrussell Mark Russell
              rhn-support-dpateriy Divyam Pateriya
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: