Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In the bpftrace flame graph representations for kernel stacks and user stacks, we do not have the name/pid number of the underlying pid calling the stack. One really needs the process name/pid number in these representations to understand what's going on.
Version-Release number of selected component (if applicable):
grafana-pcp-2.0.2-1.el8.noarch
How reproducible:
Always.
Steps to Reproduce:
1. Configure bpftrace pmda to stream data to grafana.
2. Configure grafana to use bpftrace pmda
3. View flame graphs in grafana.
Actual results:
Flame graphs without pid names and pid numbers
Expected results:
Flame graphs with "python(23123)" at the bottom to understand where the stacks are coming from.
Additional info:
Flame Graphs Dashboard can be fixed with:
You can change this line:
profile:hz:99 { @stacks[kstack] = count(); }
To this:
profile:hz:99 { @stacks[comm,kstack] = count(); }
In the Grafana panel (hover over "Kernel Stacks" -> "Edit"). For the
User stacks, replace "kstack" with "ustack". "comm" is a special
bpftrace variable containing the process name, if you'd like the PID,
you can use "pid".
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 (grafana-pcp bug fix and enhancement update), 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:4693
Description of problem: In the bpftrace flame graph representations for kernel stacks and user stacks, we do not have the name/pid number of the underlying pid calling the stack. One really needs the process name/pid number in these representations to understand what's going on. Version-Release number of selected component (if applicable): grafana-pcp-2.0.2-1.el8.noarch How reproducible: Always. Steps to Reproduce: 1. Configure bpftrace pmda to stream data to grafana. 2. Configure grafana to use bpftrace pmda 3. View flame graphs in grafana. Actual results: Flame graphs without pid names and pid numbers Expected results: Flame graphs with "python(23123)" at the bottom to understand where the stacks are coming from. Additional info: Flame Graphs Dashboard can be fixed with: You can change this line: profile:hz:99 { @stacks[kstack] = count(); } To this: profile:hz:99 { @stacks[comm,kstack] = count(); } In the Grafana panel (hover over "Kernel Stacks" -> "Edit"). For the User stacks, replace "kstack" with "ustack". "comm" is a special bpftrace variable containing the process name, if you'd like the PID, you can use "pid".