Add first/last seen and waits info to QAN Query Metrics
General
Escalation
General
Escalation
Description
Hello,
Here's a FR for PMM's QAN: the Query Metrics table is lacking "first seen", "last seen" and "min/max/avg timer wait", corresponding to columns with analogous names in performance_schema.events_statements_summary_by_digest.
This is very very useful to understand if a query has been recently introduced and also to understand if query appeared at same time than performance problems.
The first/last seen should be considered in two time ranges:
1) first/last seen all available time range
2) first/last seen in selected/current time range
How to test
None
How to document
None
AFFECTED CS IDs
CS0040298
Activity
Aaditya Dubey September 12, 2024 at 11:26 AM
Hi
Could you please confirm if you looking for any feedback from either reporter or support?
Roma Novikov October 6, 2023 at 7:24 AM
Thanks, for the report. I'm not sure we'll do it exactly this way, as for min/max/avg:
this can cover only one method of collecting data
the data collected by P_S are min/max for the period of time and can be cleaned up externally
For slow log we are already tracking the numbers and presenting them in QAN for the selected period
We will probably convert this to some "Query review" feature to check the new Queries and also compare query behavior in the selected period to all possible periods.
Hello,
Here's a FR for PMM's QAN: the Query Metrics table is lacking "first seen", "last seen" and "min/max/avg timer wait", corresponding to columns with analogous names in
performance_schema.events_statements_summary_by_digest.This is very very useful to understand if a query has been recently introduced and also to understand if query appeared at same time than performance problems.
The first/last seen should be considered in two time ranges:
1) first/last seen all available time range
2) first/last seen in selected/current time range