I tried adding group by clause in tick script as below.
stream
|from()
.database('vipl')
.measurement('Ac1')
* |groupBy(*)*
|where(lambda: "CO2_PPM" < 500)
|alert()
.message('CO2_PPM')
.id('node \'stream0\' in task \'{{ .TaskName }}\'')
.info(lambda: TRUE)
|influxDBOut()
.database('vipl')
.retentionPolicy('default')
.measurement('Alerts_test')
but no luck, with same parameters in batchsize for writing to influx , kept
as low as 50 also.
in consecutive attempts to write to influx, the amount of alerts written
back to influx varies in every attempt !
please help
On Tuesday, 27 September 2016 21:17:23 UTC+5:30, Sean Beckett wrote:
>
> It is likely that some points are considered duplicates. Without a GROUP
> BY <tags> statement on the insert, any points with the same timestamp will
> collide and be considered one point. Preserve the tags in the Alert using
> the GroupBy method
> <https://docs.influxdata.com/kapacitor/v1.0/nodes/alert_node/#groupby>.
> When written back to the database with the full tag set, the alerts should
> remain distinct even if they share a timestamp.
>
> On Tue, Sep 27, 2016 at 6:29 AM, Srikara D <[email protected]
> <javascript:>> wrote:
>
>> Hi All,
>>
>> Iam new to Influx, Kapacitor.. was trying out writing back a simple alert
>> back into influx..
>>
>> below is the tick script
>>
>> *stream*
>> * |from()*
>> * .database('vipl')*
>> * .measurement('Ac1')*
>> * |where(lambda: "**CO2_PPM**" < 450)*
>> * |alert()*
>> * .message('CO2_PPM')*
>> * .id('node \'stream0\' in task \'{{ .TaskName }}\'')*
>> * .info(lambda: TRUE)*
>> * |influxDBOut()*
>> * .database('vipl')*
>> * .retentionPolicy('default')*
>> * .measurement('Alerts_test')*
>>
>> where had set a condition on one of columns "*CO2_PPM" *to alert is less
>> than 450.
>>
>> after running a test load of data to Ac1 measurement
>>
>> 1) A query on Alert measurement gives a count of *8352*
>> *select count(CO2_PPM) from Alerts_test;*
>>
>> 2) A query on Measurement on Ac1 measurement with a same condition as
>> that of Alert gives a count of *8381*
>> * select count(CO2_PPM) from Ac1 where CO2_PPM < 450;*
>>
>> some 29 alerts are missed out when writing back to alert measurement ..
>>
>> Need help to understand the above situation
>>
>> running Influx 0.13 and kapacitor version 0.13 on FreeBSD 10.2
>>
>> Thanks
>> Srikara.D
>>
>> --
>> 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] <javascript:>.
>> To post to this group, send email to [email protected]
>> <javascript:>.
>> 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/cac19eb5-4842-446f-8c27-b5cf939ca357%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/influxdb/cac19eb5-4842-446f-8c27-b5cf939ca357%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Sean Beckett
> Director of Support and Professional Services
> InfluxDB
>
--
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/9985c2a4-54f9-4c1f-8aa5-fb531b659503%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
