Expose new pipeline metric to count the dropped messages in case of conditional evaluation fails
Open
Nobody has claimed this yet.
enhancement
metrics
status:needs-triage
- Dominant language
- Java
- Stars
- 14.9k
- Forks
- 3.5k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 88
Description
With #16322 in case of failure of evaluation of conditional statements, the offending event is simply dropped.
Add and expose a new pipeline metric to measure the count of such dropped events.
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
Start by reading the changes in #16322 to understand how conditional-evaluation failures are handled and where the offending event is dropped. Trace the existing pipeline metric exposure from that path; done means a new metric counts these dropped events and is externally visible through the pipeline metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre, stream-processing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100