Open steveh999 opened 6 years ago
Looks like what shift()
effectively does is it just shifts points' time for the duration specified. But does not make points from a shifted window()
to cache, which we expect it to do.
Some other side thing is that positive duration shifts time forward, where negative - backward in time (your samples show that, and the documentation does too - https://docs.influxdata.com/kapacitor/v1.5/nodes/shift_node).
I found an example which shows that all that was not the case in the past - https://www.influxdata.com/blog/tldr-influxdb-tech-tips-may-26-2016/.
Not sure if this a bug or a feature, but the only possible way to compare with past results is batch
, query
and offset
then.
Hi First, thanks for creating such an amazing stack, it's truly astoundingly good.
I've been trying to set up alerting using kapacitor streams and have been tearing my hair out for 2 days. I have previously successfuly created a batch query that compares a current mean value with the same mean value from an hour previous...the guts of it is this :
...and it works a treat
However when I try to so the same thing with stream data the values from "past" are always the same as the values from "current". I've even tried using chronograf to create the following task(and added the writebacks to the "backtest" db as I found in an example), but the results clearly show the values are the same.
the tickscript is :
and the output in the backtestvals db :
I've been thru the docs and looked at lots of examples so I guess I must be misunderstanding something :(
I am using influxdb 1.3.7, Telegraf 1.5.2 and Kapacitor 1.4.0
any pointers greatly appreciated
Many Thanks !!
Steve