Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-67928

Adhere to Prometheus recording rules naming to distinguish them from metrics

XMLWordPrintable

    • Update recording rules names based on Prometheus best practices
    • Quality / Stability / Reliability
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Part one of this multi release activity is done.

      Show
      Part one of this multi release activity is done.
    • None
    • Green
    • Instructions, Release Notes
    • In Progress
    • 20% To Do, 33% In Progress, 47% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Deprecated Functionality
    • Hide

      2026-02-11:
      not started....

      Show
      2026-02-11: not started....
    • Yes

      Based on the Prometheus best practices, it is advised that recording rules will follow the naming convention of <level>:<metric>:<operations>, so that is will be easy to distinguish between recording rules and metrics. Current kubevirt recording rules dont follow this convention, which causes confusion. 

      We should:

      1. Add duplicated recording rules with correct naming conventions (all repositories)
      2. Add a deprecation message for old recording rules and update the help text with [Deprecated]
      3. Update dashboards and UI to use the new recording rules
      4. Create a 4.23 item to delete the deprecated recording rules.
      5. Announce deprecations in the release notes 2 releases prior to deprecation, if possible. At least we need to announce as soon as possible to allow customers time to prepare for the deprecation.

       

              kmajcher@redhat.com Krzysztof Majcher
              sradco Shirly Radco
              Ohad Revah Ohad Revah
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: