>
>
> When passing a window to an selector function like max, only a single 
> point is returned, aka the maximum value. So keeping the original 
> "usage_idle" no longer makes sense. 
>

Maybe but, if all values are windowed why I'm still getting the other point 
in series value like usage_system? are these averages or last point of the 
window? Didn't them make the same sense once windowed than the original 
usage_idle?

I'm interested in the "max_usage_idle" but I wanted to keep the *last* 
"usage_idle" as informative, because all alerting data goes back to another 
influx database to have historical alerting data
 

>
> If you simply want all points in a window to match the alert criteria use 
> `.all()` on the alert node.
>

Good tip I'll check it. Albeit the "window + max " stuff works well, 
perhaps the "window + .all()" keeps my data intact

If I do not use .all() on a windowed stream... What am I checking? Last 
point in the window?

[snip]

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/4df36313-0b72-4d86-a0df-9aa10bd1d462%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to