prometheus / prometheus/docs

Exposition format: Define base units?

Open
#553 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

exposition format
Dominant language
TypeScript
Stars
717
Forks
1.2k
Avg merge
3d 15h
Merged PRs (30d)
19

Description

I am currently talking with @dieterbe about how/if Metrics 2.0 could be aligned with this effort and the topic of terminology and base units came up. Should we define base units and common names, like _total for counters? I think yes. It might or might not make sense to create a second ID for this, but defining it sounds worthwhile.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the issue discussion about Metrics 2.0, terminology, base units, and the _total counter suffix. No files or tests are named in the issue. Done would require an agreed scope and documented terminology, but the issue does not define who decides or where the documentation belongs.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.