IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

Have a section in query insights that shows you who is executing the query.

How this might work:

Today, when you click on the fingerprint for a query in query insights, it takes you to a detail page (“Tag details”) for that query. There could be an additional section added to this detail page listing what user executed the query. If there are a high number of executions with different users, a count of executions per user could be listed, along with the min-max range of times over which that user executed the query.

If applicable, reasons why alternative solutions are not sufficient:

The standard solution offered for finding who is executing a query is finding the query execution in logs explorer. Here is why that is insufficient:

1. There can be distinct queries that run to hundreds or thousands of lines but differ only in a few spots, and only one of them is the problem. Finding that one execution in logs explorer, when there are many similar, can be extremely difficult, if not impossible, because it can require a comparison of hundreds of lines of text between logs explorer and Query insights. This problem is exacerbated by the absence of the query fingerprint in the logs – something requested by StackDriver Feature Request #330387476.

2. Because spanner logs are so verbose and hence costly, sometimes teams choose to disable them.

3. In a troubleshooting / firefighting situation, time is of the essence. A common sequence of events is: Performance degradation is reported; DBAs review top queries and see there is a rogue query consuming disproportionate resources; DBAs then need to determine who is executing that query so they can put a stop to the issue. Today, that means turning to logs explorer and searching for the execution, which can be difficult due to reason #1. In our experience, this additional step greatly increases the time required for problem resolution. It would be much simpler if all the information we needed to resolve this common problem were in one place – Query Insights.

Other information (workarounds you have tried, documentation consulted, etc):