Manage slow queries / error queries

vesoft-inc / nebula-dashboard

Nebula Graph Service Monitor Tool

Apache License 2.0

28 stars 20 forks source link

Manage slow queries / error queries #18

Open Reid00 opened 3 years ago

Reid00 commented 3 years ago

Is your feature request related to a problem? Please describe. After building Dashboard, there are some slow queries/ error queries show up. i want to locate at which services or which queries happened, but there are no any method as i known to debug.

Describe the solution you'd like currently, no

Describe alternatives you've considered currently no

Additional context no

kqzh commented 3 years ago

You can try modify nebula-stats-exporter's config, give service a unique name, and then, build query to locate it, https://github.com/vesoft-inc/nebula-stats-exporter

nianiaJR commented 3 years ago

You can try modify nebula-stats-exporter's config, give service a unique name, and then, build query to locate it, https://github.com/vesoft-inc/nebula-stats-exporter

I think what @Reid00 means is to find the slow queries. When he finds there are slow queries show in the chart, it's meaningful to find which query caused this.

It's nice suggestion, we'll research supporting this, thanks @Reid00

nianiaJR commented 3 years ago

Is your feature request related to a problem? Please describe. After building Dashboard, there are some slow queries/ error queries show up. i want to locate at which services or which queries happened, but there are no any method as i known to debug.

Describe the solution you'd like currently, no

Describe alternatives you've considered currently no

Additional context no

I find that our ngql has supportted showing the list of all queries, which may help you get the slow quries. Here's the link:https://docs.nebula-graph.io/2.5.1/3.ngql-guide/7.general-query-statements/6.show/18.show-queries/#syntax

Reid00 commented 3 years ago

i do some tests on v2.5.1. It seems that just can query the running queries, if the query finished, output empty. In truly scenario, we cannot star at the slow queries. if queries can be logged to somewhere, may be more make sense.

bazingame commented 1 year ago

i do some tests on v2.5.1. It seems that just can query the running queries, if the query finished, output empty. In truly scenario, we cannot star at the slow queries. if queries can be logged to somewhere, may be more make sense.

Not supporting this feature until now.😅