quickwit-oss / quickwit-oss/quickwit
metrics ingested_num_bytes double counting?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
I think we are currently counting ingestion via the ingest api twice, once in quickwit/quickwit-serve/src/ingest_api/rest_handler.rs and once in quickwit/quickwit-ingest-api/src/queue.rs when dequeuing. With changes in #2950 , it's possible we also start double counting documents ingested via otlp
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
Trace ingested_num_bytes through quickwit/quickwit-serve/src/ingest_api/rest_handler.rs and quickwit/quickwit-ingest-api/src/queue.rs, then review the ingestion changes in #2950. Confirm whether the ingest API and dequeue paths both count the same bytes, including documents received through OTLP. Done means the metric counts each ingested payload once.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100