>
>
> 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
I'm trying to "soften alerts" ensuring that all the points in a window are
above the warn/crit level:
here's some of the code:
var stats = stream
|from()
.database('monitoring')
.measurement('cpu')
.where(lambda: "cpu" == 'cpu-total')
|groupBy('project', 'roles',
rt via influxql
* know the last time an alert was evaluated, and not the last time it was
evaluated to OK
On Thursday, 16 June 2016 19:39:11 UTC+2, nath...@influxdb.com wrote:
>
> Ah, yes the lambda expressions as vars was added with the 1.0 beta.
> Glad its working!
>
> On Thursday, June
mmm ok, got it :)
It seems all ok except for the
var w = lambda: "usage_idle" < 40
var c = lambda: "usage_idle" < 20
Kapacitor complains as
invalid TICKscript: parser: unexpected 9 line 1 char 9 in "var w = lambda: "
u". expected: "number","string","duration","identifier","TRUE","FALSE","==
We are tiying to define an alert flow based on measurements taken by
telegraf and stored in influx.
Started with the basic:
var stats = stream
| from()
.database('monitoring')
.measurement('cpu')
.where (lambda: "cpu" == 'cpu-total')
