Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-83867

Improved handling of removed OpenMetrics sources

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • rhel-10.1
    • pcp
    • None
    • No
    • None
    • rhel-sst-pt-pcp
    • ssg_platform_tools
    • 3
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • None
    • None
    • Unspecified Release Note Type - Unknown
    • Unspecified
    • Unspecified
    • Unspecified
    • All
    • None

      We've had a number of cases of user confusion relating to PCP metrics "hanging around" after the corresponding OpenMetrics data source has been removed from the pmdaopenmetrics configuration.  This needs to be handled in a more dynamic way, so that the metric names/instances are removed more proactively.

      Here's the latest case from John Harrigan in perf+scale ...

      I've observed with PMDA-openmetrics that metrics added and then removed remain in the name-space. For instance I added a openmetrics.workload.state metric with values. Then I stopped providing values for the 'state' metric in my scripting and now PCP tools (pminfo, pmrep) continue  to report on 'openmetrics.workload.state' as a metric with the value of N/A. Do I have to './Remove' and ./Install' openmetrics to clean this up?

       

              rh-ee-lchilton Lauren Chilton
              nathans@redhat.com Nathan Scott
              pcp-maint pcp-maint
              Jan Kurik Jan Kurik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: