influxdata / influxdata/influxdb
Tracking execution statistics of all query statements executed by a server
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Proposal:
To provide a way to track execution statistics so it can be possible to identify bad designed queries running on server.
Something similar to https://www.postgresql.org/docs/current/pgstatstatements.html.
Current behavior:
There is no way to track execution statistics of all query statements executed by a server.
Desired behavior:
A way to track execution statistics of all query statements executed by a server so it became possible to create dashboards and alarms in order to identify bad designed query statements witch can degrade the server.
Alternatives considered:
Usage of co-monitor dashboard or any statistics provided by Telegraf but information provided is not detailed enough.
Use case:
We have InfluxCloud v1 and we had our plan upgraded due to performance issues on server. Later we discovered these issues were related to bad designed queries running on server. We want a way to know the problem beforehand so we can handle it as soon as possible.
EDIT: It also helps in query optimizations... having this kind of information can help to produce periodic reports about queries impacting server so we can prioritize them for optimizations
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. Start by locating the server query-execution and statistics components, then determine the scope of collecting statement-level metrics and exposing them for dashboards; done requires a documented, usable way to inspect execution statistics for all server queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100