Request Traces of Slow Query
- Dominant language
- Python
- Stars
- 562
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
In DB Analyzer, most of the time it shows the top problematic queries.
In Elasticsearch we have the slow queries and requests with trace ID.
Fetch the request path and other details from the trace ID using monitor json log.
Expose those info to user in DB Analyzer and link to Slow Query Report + chart.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the DB Analyzer flow, the monitor JSON log handling, and the Slow Query Report and chart entry points. Trace how Elasticsearch slow-query trace IDs are available, then define how request paths and related details should be exposed and linked; done means the analyzer displays those details and links to the report and chart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, python
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100