Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd a meta metric about the scrape format #4862
Comments
This comment has been minimized.
This comment has been minimized.
|
Hmm this would mix target labels and format labels on the same time series, with potential collision resolution required. Maybe a sample value enum instead? Another metric could then define the enum values, if needed. Or we just add counters for how many endpoints in total were scraped in either format. |
This comment has been minimized.
This comment has been minimized.
|
actually I would like to see more metrics related to scrape in general, e.g. return code.. it would be metrics like "up" |
This comment has been minimized.
This comment has been minimized.
|
That's getting a bit into event logging. Keep in mind that any new time
series will be added to every single target that exists, which is not free.
…On Fri 8 Feb 2019, 23:30 Julien Pivotto ***@***.*** wrote:
actually I would like to see more metrics related to scrape in general,
e.g. return code.. it would be metrics like "up"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGyTdqmt1lFIGYcO8M4vtx0b_fQURJgqks5vLfpqgaJpZM4YbME5>
.
|
roidelapluie
closed this
Mar 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
roidelapluie commentedNov 13, 2018
With the same labels as up, I'd like to have a metric called:
scrape_format{name="openmetrics",transport="http",job="node",instance="srv01"} 1
That could ease the migration to openmetrics