summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarian Lobur <loburm@google.com>2017-06-20 15:45:41 +0200
committerGitHub <noreply@github.com>2017-06-20 15:45:41 +0200
commit94dc5f3df3c021613b1ecd870f30df4ff68b4e45 (patch)
tree794258b014d0fa657022336dafcd4c754f7c72df
parent45988676be1714cc275b8e736b42e0820aa57362 (diff)
Fix indentation for nested numerated list
In case of using two spaces github doesn't treat nested list as a separate 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.