prometheus / prometheus/graphite_exporter
How to find the metrics that are NOT matched by the rules
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 405
- Forks
- 113
- Avg merge
- 9d 5h
- Merged PRs (30d)
- 5
Description
For graphite exporter mappings i see there's a special action: "drop" for a catch-all rule that can discard the incoming that dont match.
---
- match: "."
match_type: regex
action: drop
name: "delete"
I wonder if there's a way to have a catch-all rule that saves the received metric to a file or to the stdout, so i can add track/add the unmatched metrics? I checked the statsd_exporter github and was unable to find all the possible actions there, maybe you know?
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
No source file or test is named in the issue. Start by locating the graphite exporter mapping and action handling for the shown catch-all drop rule, then determine whether unmatched metrics can be emitted to a file or stdout; done means the supported behavior and configuration are documented and covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100