-
Notifications
You must be signed in to change notification settings - Fork 79
Cyanite does not return absolute time range when it out of first resolution #281
Comments
Is there anyone with any assumption regarding the above? It's working as expected with Graphite, but not with Cyanite. |
It has to work, you are absolutely right here. Unfortunately, I have a lot of things going on at work at the moment, and was contributing to cyanite only during my free time, so I can't really help quickly. Sorry about that. |
Hi @pyr, is there any chance this one will be checked? |
@avneradania if you could help me to reproduce it, I can fix it |
Sure, how would you like to do it? |
@avneradania I assume you're using grafana not in a proxy mode or something similar, just describe your setup, if I have more questions I'll ask how more |
Our setup works as follows: |
Just wondering, why do you need |
Nit sure I understood your meaning... |
Cyanite exposes 100% compatible Grafana API, just try it in Proxy mode |
Thanks for the advice. |
@ifesdjeen, @pyr, have a chance to check this out? |
When zooming graph in Grafana, from day 29 and later, there are no data points returned and see an empty graph.
Relative time "Last X days/hours" working fine.
Absolute time inside range of first resolution, which in our case is 1m:4w, working fine.
When trying to get data from absolute time later than last 4 weeks, we get no data points and seeing empty graph.
Are you familiar with such behavior?
cyanite.yaml:
Examples:
Working POST /render(older 4 weeks):
target=AIO.DIAG.diag2.cpu.cpu.idle&from=1503888311&until=1504007603&format=json&maxDataPoints=640
Non working POST /render(later than 4 weeks):
target=AIO.DIAG.diag2.cpu.cpu.idle&from=1501626994&until=1501686700&format=json&maxDataPoints=640
The text was updated successfully, but these errors were encountered: