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 upError on ingesting samples with different value but same timestamp errors flood #2493
Comments
This comment has been minimized.
This comment has been minimized.
|
This error happens when multiple samples come in for a given series (metric name + unique labelset) for the same timestamp (likely from the same target scrape), but with a different value. This is most likely because you have a bunch of relabeling rules that just drop labels, like this:
Some of those labels are probably needed to uniquely identify the series that have them - and dropping them maps multiple series into the same labelset, which is invalid. You can't just drop labels that are needed for uniqueness. |
This comment has been minimized.
This comment has been minimized.
|
I drop labels because I do not want to create new metrics each time I recreate a container. Is there any way to drop that labels not causing any troubles? |
This comment has been minimized.
This comment has been minimized.
|
For usage questions, https://groups.google.com/forum/#!forum/prometheus-users is your best bet. |
brian-brazil
closed this
Mar 27, 2017
This comment has been minimized.
This comment has been minimized.
xixikaikai
commented
Jun 19, 2017
|
I've also the same question, but I do not know which metric causing the trouble, and prometheus log does not show this error, only the msg="Error on ingesting samples with different value but same timestamp" |
xixikaikai
referenced this issue
Jun 19, 2017
Closed
Error on ingesting samples with different value and the prometheus log does not show #2858
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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. |
onorua commentedMar 12, 2017
What did you do?
Upgraded to 1.5.2 and run it for some time.
Environment and logs
Dockerized Prometheus node with 256GB of RAM and 12cores, monitoring around 1.5k nodes, at least 3 endpoints on each host.