[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-06-28 Thread Archie Archbold
#x27;, 'device') > > > |alert() > > > .warn(lambda: "used_percent" >= 80) > > > .warnReset(lambda: "used_percent" < 80) > > > .crit(lambda: "used_percent" >= 90) > > > .c

[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-06-26 Thread Archie Archbold
t; > > > stream > > > |from() > > > .database('telegraf') > > > .measurement('disk') > > > .groupBy('host', 'device') > > > |alert() > > > .warn(lambd

[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-02-22 Thread Archie Archbold
alerts use the `.noRecoveries` property of > the alert node. This will suppress the OK alerts. > > On Friday, February 17, 2017 at 3:33:16 PM UTC-7, Archie Archbold wrote: >> >> Hey all. Pretty new to TICK but I have a problem that I can't wrap my >> head around. >

[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-02-22 Thread Archie Archbold
sage\u0026#34;:\u0026#34;DISK SPACE WARNING Server:jira.hostname.xyz Path: /var/log/audit USED PERCENT: 5.053099187894773\u0026#34;}\n","time":"2017-02-22T23:27:10Z","duration":9223372036854775807,"level":"OK","data":{"Series"

[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-02-22 Thread Archie Archbold
WARNING Server:jira.spawar.navy.mil Path: /var/log/audit USED PERCENT: 5.053099187894773\u0026#34;}\n","time":"2017-02-22T23:27:10Z","duration":9223372036854775807,"level":"OK","data":{"Series":[{"name":"di

[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-02-22 Thread Archie Archbold
fstype":"ext3","host":"name-fusion.hostname.xyz","path":"/var"},"Fields":{"free":1289412608,"inodes_free":636979,"inodes_total":655360,"inodes_used":18381,"total":10568916992,"use

[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-02-22 Thread Archie Archbold
ler? > > On Wednesday, February 22, 2017 at 12:23:53 PM UTC-7, Archie Archbold > wrote: >> >> Thanks so much for the reply. I do want the recovery alerts, but the >> problem is that when I start kapacitor, the task sees *any* server/path >> in an up status as a recov

[influxdb] Re: kapacitor sending ok alerts as state change on start up

2017-02-22 Thread Archie Archbold
rts use the `.noRecoveries` property of > the alert node. This will suppress the OK alerts. > > On Friday, February 17, 2017 at 3:33:16 PM UTC-7, Archie Archbold wrote: >> >> Hey all. Pretty new to TICK but I have a problem that I can't wrap my >> head around. >> >&g

[influxdb] kapacitor sending ok alerts as state change on start up

2017-02-17 Thread Archie Archbold
Hey all. Pretty new to TICK but I have a problem that I can't wrap my head around. I am monitoring multiple servers all sending data to one influxdb database and using the 'host' tag to separate the servers in the DB My 'disk' measurement is taking in mulitiple disk paths from the servers (HO

[influxdb] kapacitor not comparing data independently

2017-02-16 Thread Archie Archbold
Hey all. Pretty new to TICK but I have a problem that I can't wrap my head around. I am monitoring multiple servers all sending data to one influxdb database and using the 'host' tag to separate the servers in the DB My 'disk' measurement is taking in mulitiple disk paths from the servers (HO

[influxdb] Re: Kapacitor email alert not working

2016-12-28 Thread Archie Archbold
Don't know if you are still having problems with this but when I ran into this I found that if I did not put in a 'from' attribute, the task would fail to start. Right now you have: from = "" when it should be: from = "someemailaddr...@somehost.com" On Thursday, October 20, 2016 at 1:56:41 PM

[influxdb] defining and starting kapacitor tasks in configuration

2016-12-15 Thread Archie Archbold
Hey all. Sorry if this is a noob question but I was wondering if there is a way to define and start tasks in the kapacitor.conf file. I am running my TICK stack within docker containers and would like to automate the entire process. Right now I am having docker-compose call a script to define th