Clean up graphite exporter definition
Open
Nobody has claimed this yet.
team: workbench
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Connected to #46
We fixed a small bug in host name detection (excluding dashes). However, we should harden this a bit:
- Make sure that Connect has the same flexibility to customize
mappingYamlwith values - (probably unnecessary) pull into a library helper
- Figure out what characters are actually allowed in docker / kubernetes / helm as hostnames, so we can be sure that our regex captures all of them
It's also possible that the product will beat us to actually expose prometheus metrics and save us some work 😄
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 reviewing the graphite exporter definition and the connected #46 issue, then trace how Connect customizes mappingYaml. Confirm the allowed hostname characters for Docker, Kubernetes, and Helm and decide whether the logic belongs in a shared helper. Done means both customization paths are covered and the hostname matching behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100