diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-09-09 09:25:18 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-09-09 09:25:18 -0700 |
| commit | 6a176d6df889c2d5d3fffb1818b9b1f4b416a6b4 (patch) | |
| tree | 4ae44d2dd692fe9f10b34762655654e243b300b2 | |
| parent | 2ca62cf8f3bc6a20571274a1d78d979bc08ddf5c (diff) | |
| parent | 6a13552926f19127e4bd00f8530ea2c9004b6341 (diff) | |
Merge pull request #4072 from brancz/patch-1
contributors/devel/sig-instrumentation: Add further details on naming best practices
| -rw-r--r-- | contributors/devel/sig-instrumentation/instrumentation.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/contributors/devel/sig-instrumentation/instrumentation.md b/contributors/devel/sig-instrumentation/instrumentation.md index b0a11193..7595b436 100644 --- a/contributors/devel/sig-instrumentation/instrumentation.md +++ b/contributors/devel/sig-instrumentation/instrumentation.md @@ -90,7 +90,8 @@ apply additionally. ## Naming -Metrics added directly by application or package code should have a unique name. +General [metric and label naming best practices](https://prometheus.io/docs/practices/naming/) apply. +Beyond that, metrics added directly by application or package code should have a unique name. This avoids collisions of metrics added via dependencies. They also clearly distinguish metrics collected with different semantics. This is solved through prefixes: |