huyuanfeng2018 commented on pull request #12042: URL: https://github.com/apache/druid/pull/12042#issuecomment-989379860
> identifying what queries are taking longer can and should be done in the system, druid is emitting metrics to. That will be much more flexible than configuring a threshold in druid services and changing such a threshold will require a restart. > > Druid should already be emitting query-id along with the time. In the metric store that you are using, you can filter the query ids based on the time taken and then find the actual queries in the logs corresponding to those ids. does that not work for you? Of course it works! But I want to count the number and proportion of these longquery occurrences in druid, which is reflected in the metric, so that I can quickly judge the number of long queries that take a long time through the metric information. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
