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 upConsider reducing label cardinality for persist error exporting #496
Comments
This comment has been minimized.
This comment has been minimized.
|
From quick look this should be a no-label counter, it's already in the logs. |
juliusv
closed this
in
9412b29
Feb 1, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
juliusv commentedJan 31, 2015
Currently we export the label
error="<entire error string>"for persist errors on the metricprometheus_local_storage_persist_errors_total:prometheus/storage/local/storage.go
Line 539 in f541390
In a Prometheus whose disk just ran full, this already produced two different error strings:
Conceivably there could be many more different offsets affected, so we should probably clamp down the label cardinality on this one.
/cc @beorn7