summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrian Grant <bgrant0607@users.noreply.github.com>2017-06-20 23:56:15 -0700
committerGitHub <noreply@github.com>2017-06-20 23:56:15 -0700
commit6a99cd760f2278672179f082e2874e2c51b4ccb5 (patch)
treee5e5ffa7f94e044c7d8ae07fd5244c383b37f299
parentd08e5a67b6cbd544b74c2ca8d3ad4d9ff18f81bf (diff)
parent94dc5f3df3c021613b1ecd870f30df4ff68b4e45 (diff)
Merge pull request #738 from loburm/patch-1
Fix indentation for nested numerated list
-rw-r--r--contributors/devel/instrumentation.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/contributors/devel/instrumentation.md b/contributors/devel/instrumentation.md
index 66992e40..d54bb45a 100644
--- a/contributors/devel/instrumentation.md
+++ b/contributors/devel/instrumentation.md
@@ -28,14 +28,14 @@ The following describes the basic steps required to add a new metric (in Go).
2. Create a top-level var to define the metric. For this, you have to:
- 1. Pick the type of metric. Use a Gauge for things you want to set to a
+ 1. Pick the type of metric. Use a Gauge for things you want to set to a
particular value, a Counter for things you want to increment, or a Histogram or
Summary for histograms/distributions of values (typically for latency).
Histograms are better if you're going to aggregate the values across jobs, while
summaries are better if you just want the job to give you a useful summary of
the values.
- 2. Give the metric a name and description.
- 3. Pick whether you want to distinguish different categories of things using
+ 2. Give the metric a name and description.
+ 3. Pick whether you want to distinguish different categories of things using
labels on the metric. If so, add "Vec" to the name of the type of metric you
want and add a slice of the label names to the definition.