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 upexpand series set: series not found #3188
Comments
JorritSalverda
changed the title
Actual interval larger then defined in version 2 beta 3
Gaps in data in version 2 (beta 3)
Sep 18, 2017
This comment has been minimized.
This comment has been minimized.
|
This is due to the new staleness handling. The actual issue here is likely that those are cAdvisor metrics, which are broken as of recent versions, see: google/cadvisor#1704 However, the 'series not found' errors are likely unrelated and a bit concerning. |
This comment has been minimized.
This comment has been minimized.
|
I'm indeed using cAdvisor as bundled in Google Container Engine, so I'll wait for the fix to be included in a future release. I think (at least part of) the 'series not found' errors are caused by alert rules I use in all my Prometheus servers, but are only applicable for some of them. Mostly for CockroachDB which I only run in one of my clusters. Do alert and aggregation rules looking for non-existing timeline series indeed result in that kind of error? |
brian-brazil
added
the
kind/bug
label
Sep 28, 2017
brian-brazil
changed the title
Gaps in data in version 2 (beta 3)
expand series set: series not found
Sep 28, 2017
brian-brazil
added
component/local storage
dev-2.0
labels
Sep 28, 2017
This comment has been minimized.
This comment has been minimized.
|
@JorritSalverda @grobie could you report whether this is resolved in rc.1? |
This comment has been minimized.
This comment has been minimized.
|
Confirmed! |
fabxc
closed this
Oct 18, 2017
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. |
JorritSalverda commentedSep 18, 2017
Since testing version 2.0 beta we see more gap than graph in a lot of our Grafana graphs, making a cpu graph look like this.
The graph uses the following query:
When graphing this in the Prometheus GUI it shows the same gaps. Increasing the duration for irate doesn't help.
Both
sum(irate(container_cpu_usage_seconds_total{container_name="prometheus"}[30s])) by (container_name)andsum(container_spec_cpu_shares{container_name="prometheus"} / 1024) by (container_name)exhibit gaps, although not necessarily at the same time, so the resulting query has even more gaps.In our Prometheus server we use the following intervals:
When counting the number of values recorded in 5 minutes using
container_cpu_usage_seconds_total{container_name="prometheus"}[5m]it only has about 13 of them. That's approximately every 25 seconds, not 10 as configured.In Prometheus 1.7.1 and before these graphs looked fined. I'm not sure whether the actual interval was any different or the duration for which the last value of a timeline shows up in a query has decreased in 2.0.
Any ideas what causes it and how to fix?
Environment
Linux 4.4.64+ x86_64