prometheus / prometheus/client_python
Set label-specific timestamps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 876
- Avg merge
- 8d 4h
- Merged PRs (30d)
- 1
Description
Issue #588 describes a way to set a timestamp for a whole metric using a custom collector. However, this solution does not work if different timestamps for different labels are required (e.g. a metric temperature with label source=node1 and source=node2) a more specific setting is described here and additional reasoning for this feature can be found here.
As issue #588 is closed and does not seem to get much attention anymore I decided to create a new issue for this more specific use case.
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 issue #588 and the two linked comments, which describe the existing custom-collector approach and the requested label-specific behavior. Define what support for distinct timestamps on each label set should look like and verify it against the temperature example.
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
- 25/100