Remove truncated queries from QAN, or give better feedback
General
Escalation
General
Escalation
Description
Queries that get truncated by MySQL (due to too small performance_schema_max_digest_length), get scanned by PMM in truncated state. These examples are non-useful in QAN since you cannot use Explain and cannot use Tables tabs. PMM should purge these examples on a frequency basis (eg: daily, or weekly).
If you disagree with auto-purge, then give users the ability to purge them via UI or API.
Queries that are truncated cause Explain to “spin forever”, and show red grafana error boxes in the upper corner. This creates a bad user experience. It would be far better to show something like ‘Query cannot be explained due to truncation.’ than cryptic “invalid symbol” error messages.
How to test
None
How to document
None
Activity
Roma Novikov
November 6, 2024 at 9:14 AM
PMM stores in QAN the flag about “trancated“ query, so this is what should be used to not run explain on such queries. I suspect, there might be. cases when flag is not set but the query is not full
Medium
Queries that get truncated by MySQL (due to too small performance_schema_max_digest_length), get scanned by PMM in truncated state. These examples are non-useful in QAN since you cannot use Explain and cannot use Tables tabs. PMM should purge these examples on a frequency basis (eg: daily, or weekly).
If you disagree with auto-purge, then give users the ability to purge them via UI or API.
Queries that are truncated cause Explain to “spin forever”, and show red grafana error boxes in the upper corner. This creates a bad user experience. It would be far better to show something like ‘Query cannot be explained due to truncation.’ than cryptic “invalid symbol” error messages.