Time range "with lenses"
- Dominant language
- Go
- Stars
- 11.7k
- Forks
- 802
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 80
Description
The current implementation of time range selector represents a time series illustrating the sum of all profiling samples over a given time range. However, when dealing with wide time spans (e.g., a week or a few days), queries for specific events might take a considerable amount of time, potentially leading to timeouts.
In the Explore view we allow users to pick one of "Metric", "Profile", "Both", however, switching between them might be rather inconvenient and I don't know if anyone uses it actually:
---
I propose to make the main time range selector similar to what we have in the diff view. In this approach, stack traces are retrieved and visualized only for the selected area, with the date-time picker controlling the outer window. This should enhance the user experience, especially for cases where users only need to identify specific events such as CPU time surges or memory consumption spikes.
By default, the selected area should be reasonably short, like an hour, to prevent users from fetching excessive data.
This feature is expected to complement the [heatmap](https://github.com/grafana/pyroscope/issues/3015) and [profile entries](https://github.com/grafana/pyroscope/issues/3016) proposals, providing users with a more efficient way to pinpoint and analyze specific events within the profiling data.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.