wu-sheng opened a new issue, #12249: URL: https://github.com/apache/skywalking/issues/12249
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar feature requirement. ### Description By adopting BanyanDB as first-class storage, we are going to keep adding observability to ourself, as we have more capability to optimize performance. So here, after @hanahmily and I had a discussion, I want to propose a new debugging tool for MQE query.ourselves ### Use case MQE is the most important query engine right now for several versions. Since v10, MQE + BanyanDB storage are recommended as always. In order to help end users, we hope to diagnose the performance easier in collecting context and end-to-end performance costs. To implement that, we need to add things as following - [ ] 1. BanyanDB 0.7 implemented structured execution plans with an on-demand flag. This requires an extension for a query. When its client runs a query with that flag, it should return the data with execution plans from the server side. - [ ] 2. A new optional GraphQL flag and response extension for MQE, which could drive the engine to build an execution process tree(like an internal self-trace), including the calling methods(such as metric query, and sort query). When the storage has server-side plans, such as <1>, we could wrap them inside the trace segments. - [ ] 3. As the newly added flag from <2> is optional, UI should have the capability to visualize this trace on-demand. We need to discuss how to visualize this. Maybe through a pop-up debug box aside from the widget, and showing the MQE debugging trees one by one. Also, considering the query refreshing, the UI should be able to hold 5 to 10 recent query logs. ### Related issues _No response_ ### Are you willing to submit a pull request to implement this on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
