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 upReturns no data when the metric in right side of `or` operator does not exist on InfluxDB #5466
Comments
This comment has been minimized.
This comment has been minimized.
|
I don't see how InfluxDB returning a 500 is an issue with Prometheus. |
This comment has been minimized.
This comment has been minimized.
|
Is this Prometheus's expected behavior? Prometheus returns no data when the query right hand of |
This comment has been minimized.
This comment has been minimized.
|
If a remote storage returns an error, we ignore all data from it. It'd be too hard to reason about otherwise. |
This comment has been minimized.
This comment has been minimized.
|
I understand. Thanks a lot for very quick response! |
hirose31
closed this
Apr 16, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hirose31 commentedApr 16, 2019
Bug Report
What did you do?
send following query
What did you expect to see?
return metrics reading from local storage and remote storage (InfluxDB).
What did you see instead? Under which circumstances?
return only metrics reading from local storage.
Environment
System information:
Linux 4.15.0-29-generic x86_64
Prometheus version:
InfluxDB version:
1.7.4
Detail
query using
oroperator likeVECTOR1 or VECTOR2to Prometheus.metrics of VECOTR1 exist in both Prometheus and InfluxDB
metrics of VECOTR2 does not exist in both Prometheus and InfluxDB
Prometheus returns metrics (
VECTOR1) in Prometheus (within--storage.tsdb.retention.time)Prometheus query to InfluxDB metrics of
VECTOR1andVECTOR2InfluxDB returns metrics of
VECTOR1InfluxDB returns
500 Internal Server Erroras response of queryVECTOR2Prometheus returns no data in InfluxDB (over
--storage.tsdb.retention.time)The following graphs: