Summary of Open Issue: Show Trace ID in Querier UI for Thanos
Issue Overview
Submitted by: fpetkovski Date: 2022-08-26 Status: Active discussion; no recent activity updates
Problem: While troubleshooting query performance in the Thanos querier, developers find it difficult to access the trace ID for specific queries. Currently, the trace ID is only available as a response header, which is truncated and requires using network inspection tools to retrieve, making it not user-friendly or efficient for debugging.
Proposed Solution
- UI Enhancement: Display the full trace ID in the querier user interface next to existing PromQL-related stats.
- Tracing Tags: Include the trace ID in the query’s tracing tags for better visibility.
Alternatives Considered
- Developers currently access the trace ID through response headers, which is cumbersome and requires manual lookup in tracing systems.
- A suggestion was made to implement a history of slow queries similar to existing solutions in other database systems, possibly using an embedded SQLite for storage.
Discussion Points
- Feature Scope: While the original proposal focuses on displaying the trace ID, a contributor (yeya24) suggested that capturing metadata for historical queries could enhance the usability of Thanos.
- Storage Needs: There are differing views on whether maintaining historical query data is necessary. Some contributors, like fpetkovski, are primarily interested in immediate trace ID visibility rather than historical analysis.
- Potential for Expansion: The conversation hints at the possibility of developing a larger feature set, including slow query logs and a more comprehensive query history, potentially warranting further exploration through GSoC or similar initiatives.
Contributor Activity
- The issue has garnered interest from multiple contributors, with intentions to work on it expressed by individuals such as Vaani-pathariya and jatinagwal. Guidance on technical requirements (e.g., ReactJS setup) has been sought, indicating a readiness to move forward with development.
Labels
- Difficulty: Easy
- Feature Request/Improvement
- Good First Issue
This issue highlights a clear need for improving the query troubleshooting capabilities in Thanos, specifically around traceability and visibility of trace IDs, fostering an environment for collaborative development towards meaningful enhancements.
