Open zz-jason opened 3 years ago
For slow query, maybe it is better to include the information from information_schema.statements_summary
? I would also add bind_info to the list of sources.
both information_schema.statements_summary
and bind_info
is helpful for investigation.
@breeswish It would be better if we can support collecting these metrics in TiDB Dashboard.
The idea is great. Tracing & metrics can be supplied as well. I only concern about the implementation for some parts. For example:
As a reference, CockroachDB may have something similar: https://www.cockroachlabs.com/docs/stable/admin-ui-statements-page.html#diagnostics
Feature Request
Is your feature request related to a problem? Please describe:
To investigate a slow query, typically we need the following information:
create table
statements for related tablesexplain analyze ...
, usually contained in slow logCollecting these metrics is not easy, it involves lots of discussion with users and explanations. If we could collect all the needed information, it would greatly save the time to collect useful information and reduce the time to find the slow reason.
Describe the feature you'd like:
explain analyze format = zip ...
statement to collect all the needed information, putting them to a zip file, then users can provide us the zip file to help investigate the root cause.Describe alternatives you've considered:
N/A
Teachability, Documentation, Adoption, Migration Strategy:
N/A