Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/concepts/jobs_instances.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,15 @@ the following time series:
* `scrape_series_added{job="<job-name>", instance="<instance-id>"}`:
the approximate number of new series in this scrape. *New in v2.10*

if you enable [`extra-scrape-metrics` feature](/docs/prometheus/latest/feature_flags/#extra-scrape-metrics), you will also get:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are already documented below.
I think a more important change would be to document that they should be enabled by configuration and that the feature flag is being phased out . See prometheus/prometheus#17606


* `scrape_timeout_seconds{job="<job-name>", instance="<instance-id>"}`:
the configured scrape timeout for a target.
* `scrape_sample_limit{job="<job-name>", instance="<instance-id>"}`:
the configured sample limit for a target.
* `scrape_body_size_bytes{job="<job-name>", instance="<instance-id>"}`:
the uncompressed size of the most recent scrape response, if successful.

The `up` time series is useful for instance availability monitoring.

With the [`extra-scrape-metrics` feature flag](/docs/prometheus/latest/feature_flags/#extra-scrape-metrics) several additional metrics are available:
Expand Down