RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1784862 - Wildcard legends in Grafana-PCP
Summary: Wildcard legends in Grafana-PCP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: grafana-pcp
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Andreas Gerstmayr
QA Contact: Jan Kurik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-18 14:19 UTC by Lukas Zapletal
Modified: 2021-09-17 12:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:58:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:1681 0 None None None 2020-04-28 15:58:15 UTC

Description Lukas Zapletal 2019-12-18 14:19:30 UTC
Description of problem:

I am trying PCP 5.0.2 with the all-new Grafana and so far so good, but I have a problem with displaying multiple metrics on a single graph. Say I want to display disk.dev.* all on one graph. If I put this to the query (with the wildcard) it wimply renders two dozens of legends with "vda". Not very useful, when I try to put $metric to the label field I expect the legend to show full metric name, however it simply displays "disk.dev.*" for all legends. There is also quite useful variable $metric0 which is exactly what I want (to display the last element of the metric name), however it displays "*" for all legends again.

I've managed to display "Value" for all legends too, however I am unable to reproduce this with standard metrics only with my own data. Here is the archive, the metric tree in question is:

mmv.fm_rails_activerecord_instances.*

These are counters of some object instances, for some reason PCP instance is not used (this has been fixed with statsd PMDA in PCP5 however I still need to be able to send from old version).

https://lzap.fedorapeople.org/temp/mmv-grafana-labels.tar.xz

Version: 5.0.2-1

Comment 1 Andreas Gerstmayr 2019-12-18 14:37:57 UTC
Bug is confirmed and fixed in upstream (1.x branch):

commit c178548bb96d823444e3cfcc53d69477e80a2471
Author: Andreas Gerstmayr <agerstmayr>
Date:   Wed Dec 18 12:29:09 2019 +0100

    redis: support wildcards in metric names

Comment 2 Andreas Gerstmayr 2020-01-07 14:12:39 UTC
Bug is fixed in grafana-pcp 1.0.5-2

Comment 4 Jan Kurik 2020-01-15 10:34:38 UTC
Legend "$metric" and "$metric0" works as expected when using grafana-pcp 1.0.5-2 build.

Comment 6 errata-xmlrpc 2020-04-28 15:58:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1681


Note You need to log in before you can comment on or make changes to this bug.