mozilla-services / mozilla-services/markus
Implement tags in Statsd backend creating additional metrics
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 70
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Would it make sense that for a given metric A, using tags, to create additional metrics for each tag?
For example, for calls:
incr('A')
incr('A', tags=dict(tag1=value1, tag2=value2))
incr('A', tags=dict(tag2=value2))
It would generate metrics:
- A.count = 3
- A.tagged.tag1.value1.count = 1
- A.tagged.tag2.value2.count = 2
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 locating the Statsd backend and reviewing its existing metric and tag handling. Clarify the aggregation and naming behavior for tagged metrics, then verify that the implementation produces the issue's A.count and A.tagged.*.count examples, including repeated and partially tagged calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100