Skip to content

Best Practice Docs Don't Call Out the Importance of Job Label #2690

Description

@conallob

https://prometheus.io/docs/practices/naming/ and https://prometheus.io/docs/practices/rules/ should call out the importance of the job label, particularly in a multi-tenant prometheus installation.

https://prometheus.io/docs/practices/naming/ does not mention the job label at all.

https://prometheus.io/docs/practices/rules does mention

Always specify a without clause with the labels you are aggregating away. This is to preserve all the other labels such as job, which will avoid conflicts and give you more useful metrics and alerts.

and all it's examples include an explicit job label

But that's about as explicit as it gets.

Activity

  1. conallob commented on Jul 15, 2025

    @conallob
    Author

    As somebody who has been writing PromQL for much longer than it was called PromQL (IYKYK), I'm happy to take this on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementImprovements to existing documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions