aquasecurity / aquasecurity/tracee
Add metrics for event travel time in the pipeline
Open
area/performance
kind/feature
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 507
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
We should be able to know the time it takes an event to travel in the pipeline from decode to sink stages.
The metrics should be per event type so we can know which events consume more time in the pipeline
Contributor guide
Research direction
No files or tests are named. Start by tracing the pipeline from the decode stage through the sink stage and locating existing metrics instrumentation. Define how elapsed travel time will be recorded per event type, then verify that the resulting metrics distinguish event types and cover the full pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100