grafana / grafana/pyroscope

Feedbacks on Grafana UI

Open
#2,804 3 comments 2 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
11.7k
Forks
802
Avg merge
1d 19h
Merged PRs (30d)
80

Description

We have been comparing flamgraph representation in both Pyroscope and Grafana. Both look great, our feeling is that Pyroscope's UI is more user friendly.
Here is a couple of unsorted feedbacks:

### Easier zoom in/out

In Pyroscope you can zoom in/out on a particular node with a single click.
To do that in Grafana you need, two clicks: first on the node then on *focus block*

feature request: in Grafana use left click to zoom in/out, use right click to show the menu

### Hover on table view

When you hover a line in the table you have the information about the node. Moreover the line on which we hover is highlighted
You don't have those information in Grafana.
![Capture d’écran 2023-12-05 à 11 27 50](https://github.com/grafana/pyroscope/assets/12611310/04f0a343-270d-424a-b79b-e1cd3ec1eed2)

feature request: add the hover in Grafana table

### Clearer hover popup in Pyroscope

We find the hover popup in the flamegraph more readable / clearer in Pyroscope where the information are shown in a formatted table. Whereas in Grafana, its a couple of lines of text.
The content is also easier to understand in Pyroscope: (share of cpu, cpu time, samples) vs (total, self, samples)

In Pyroscope:
![Capture d’écran 2023-12-05 à 11 31 53](https://github.com/grafana/pyroscope/assets/12611310/85a5ec37-7404-49af-a0fd-ec83a1c160e8)

In Grafana:
![Capture d’écran 2023-12-05 à 11 31 35](https://github.com/grafana/pyroscope/assets/12611310/e05770da-5527-4b70-afa4-4c2cfb8afd26)

### Gauge in table view

The table view in Pyroscope show colored gauge for *self* and *total* cells. On Grafana you cannot visually identify an eventual bottleneck as you need to read each line.
see: Hover on table view's screenshot.
note: The color is the same in the table and in the flamgraph.

feature request: add the gauge in Grafana table + allow to configure the default colorscheme to use for a given pyroscope data source (*by value* vs *by package*).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.