This repository was archived by the owner on Aug 23, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 107
errors like "invalid request. to must > from" #912
Labels
Milestone
Comments
I can reproduce like so:
|
Dieterbe
added a commit
that referenced
this issue
May 17, 2018
if interval is, say 120s then you can expect points with these timestamps: 120 240 360 ... previously, if you issued a render request such as to=300,until=330 on a raw archive (which still needs quantizing so we do some tricks) those tricks would result in bad request errors. Now we handle them as they should: return []. fix #912
Dieterbe
added a commit
that referenced
this issue
May 17, 2018
if interval is, say 120s then you can expect points with these timestamps: 120 240 360 ... previously, if you issued a render request such as to=300,until=330 on a raw archive (which still needs quantizing so we do some tricks) those tricks would result in bad request errors. Now we handle them as they should: return []. fix #912
Dieterbe
added a commit
that referenced
this issue
May 18, 2018
if interval is, say 120s then you can expect points with these timestamps: 120 240 360 ... previously, if you issued a render request such as to=300,until=330 on a raw archive (which still needs quantizing so we do some tricks) those tricks would result in bad request errors. Now we handle them as they should: return []. fix #912
Dieterbe
added a commit
that referenced
this issue
May 18, 2018
if interval is, say 120s then you can expect points with these timestamps: 120 240 360 ... previously, if you issued a render request such as to=300,until=330 on a raw archive (which still needs quantizing so we do some tricks) those tricks would result in bad request errors. Now we handle them as they should: return []. fix #912
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
thanks to jaeger I see (trace 6c3a75072bd1fef1, a0e316731c4c65):
HTTP POST getdata ->
getTargetsLocal with these properties:
--> getSeriesAggMetrics
what I think happens:
getTargetsLocal calls
getTarget. readRollup false, normalize false
calls s.getSeriesFixed with consolidation.None
calls newRequestContext, which does this:
and:
calls s.getSeries
calls getSeriesAggMetrics
calls metric.Get
calls AggMetric.Get
which triggers:
The text was updated successfully, but these errors were encountered: