Skip to content

Commit 7ab2651

Browse files
authored
Add more info to writing exporters (#2553)
Add some additional best practice notes to the "writing exporters" best practices guide. Signed-off-by: SuperQ <[email protected]>
1 parent 385e577 commit 7ab2651

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

content/docs/instrumenting/writing_exporters.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -374,6 +374,12 @@ and the metric name prefixed by the exporter name, for example
374374
if the exporter also makes sense to use as just a collector, then
375375
definitely exclude it.
376376

377+
Other scrape "meta" metrics should be avoided. For example, a counter for
378+
the number of scrapes, or a histogram of the scrape duration. Having the
379+
exporter track these metrics duplicate the [automatically generated
380+
metrics](docs/concepts/jobs_instances/#automatically-generated-labels-and-time-series)
381+
of Prometheus itself. This adds to the storage cost of every exporter instance.
382+
377383
### Machine and process metrics
378384

379385
Many systems, for example Elasticsearch, expose machine metrics such as

0 commit comments

Comments
 (0)