influxdata / influxdata/kapacitor
kapacitor filter data?
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Hello, I'm curious about why the points were lost between log2 and alert3. Does kapacitor filter data?
Here is my Kapacitor version
$ kapacitor version
Kapacitor 1.3.1 (git: master 3b5512f7276483326577907803167e4bb213c613)
dev@debian:~/yqf/test$ kapacitor show admin_test
ID: admin_test
Error:
Template:
Type: stream
Status: enabled
Executing: true
Created: 06 Mar 18 13:39 CST
Modified: 07 Mar 18 17:43 CST
LastEnabled: 07 Mar 18 17:43 CST
Databases Retention Policies: ["game"."autogen"]
TICKscript:
stream
|from()
.database('game')
.retentionPolicy('autogen')
.measurement('equity_summary2')
|log()
|alert()
.id('{{ .TaskName }}')
.message('{{ .TaskName }} is {{ .Level }} value:{{ .Fields }}')
.warn(lambda: "volume" < float('5.0e+02'))
.crit(lambda: "margin" < float('5.0e+03'))
.log('/tmp/alert.log2')
.mode(0644)
.tcp('localhost:3309')
|influxDBOut()
.database('rule_alert')
.retentionPolicy('default')
.measurement('alert_test2')DOT:
digraph admin_test {
graph [throughput="0.00 points/s"];stream0 [avg_exec_time_ns="0s" errors="0" working_cardinality="0" ];
stream0 -> from1 [processed="19"];from1 [avg_exec_time_ns="0s" errors="0" working_cardinality="0" ];
from1 -> log2 [processed="19"];log2 [avg_exec_time_ns="0s" errors="0" working_cardinality="0" ];
log2 -> alert3 [processed="19"];alert3 [alerts_triggered="8" avg_exec_time_ns="13.456795ms" crits_triggered="5" errors="0" infos_triggered="0" oks_triggered="3" warns_triggered="0" working_cardinality="1" ];
alert3 -> influxdb_out4 [processed="8"];influxdb_out4 [avg_exec_time_ns="11.096µs" errors="0" points_written="8" working_cardinality="0" write_errors="0" ];
Here are the all 19 points
equity_summary2 uid=665,equity=110000,pos_profit=18221,margin=685,commision=32538,settled_pl=13119,unsettled_pl=10814,pl=24847,volume=17468
equity_summary2 uid=145,equity=110000,pos_profit=27835,margin=2241,commision=8476,settled_pl=14536,unsettled_pl=687,pl=20875,volume=28649
equity_summary2 uid=663,equity=110000,pos_profit=611,margin=5486,commision=15618,settled_pl=22137,unsettled_pl=17231,pl=14298,volume=25925
equity_summary2 uid=749,equity=110000,pos_profit=21899,margin=27548,commision=21433,settled_pl=20597,unsettled_pl=15204,pl=17648,volume=2976
equity_summary2 uid=202,equity=110000,pos_profit=12978,margin=21534,commision=29510,settled_pl=14123,unsettled_pl=10069,pl=30053,volume=5801
equity_summary2 uid=129,equity=110000,pos_profit=23653,margin=20264,commision=1043,settled_pl=15445,unsettled_pl=11573,pl=10911,volume=15985
equity_summary2 uid=741,equity=110000,pos_profit=17251,margin=21926,commision=6540,settled_pl=15599,unsettled_pl=10437,pl=10290,volume=28571
equity_summary2 uid=333,equity=110000,pos_profit=7615,margin=4730,commision=3231,settled_pl=20534,unsettled_pl=9279,pl=22073,volume=9757
equity_summary2 uid=98,equity=110000,pos_profit=8951,margin=20992,commision=2874,settled_pl=19020,unsettled_pl=30516,pl=6581,volume=9975
equity_summary2 uid=669,equity=110000,pos_profit=5245,margin=23433,commision=15199,settled_pl=23939,unsettled_pl=332,pl=15718,volume=7574
equity_summary2 uid=275,equity=110000,pos_profit=9002,margin=31160,commision=8750,settled_pl=6284,unsettled_pl=18248,pl=28002,volume=20616
equity_summary2 uid=744,equity=110000,pos_profit=15350,margin=599,commision=11526,settled_pl=5417,unsettled_pl=17272,pl=11960,volume=3125
equity_summary2 uid=432,equity=110000,pos_profit=26465,margin=11980,commision=19766,settled_pl=11313,unsettled_pl=18637,pl=16563,volume=26204
equity_summary2 uid=588,equity=110000,pos_profit=7326,margin=20623,commision=25611,settled_pl=13827,unsettled_pl=5931,pl=12358,volume=25266
equity_summary2 uid=924,equity=110000,pos_profit=18386,margin=27479,commision=27430,settled_pl=8326,unsettled_pl=16609,pl=3553,volume=9183
equity_summary2 uid=423,equity=110000,pos_profit=10678,margin=22644,commision=163,settled_pl=25076,unsettled_pl=894,pl=24943,volume=25149
equity_summary2 uid=535,equity=110000,pos_profit=16899,margin=13445,commision=28289,settled_pl=133,unsettled_pl=15655,pl=1851,volume=24354
equity_summary2 uid=586,equity=110000,pos_profit=21497,margin=10903,commision=11160,settled_pl=14952,unsettled_pl=15081,pl=19587,volume=16533
equity_summary2 uid=31,equity=110000,pos_profit=32594,margin=4967,commision=2862,settled_pl=7442,unsettled_pl=12989,pl=12411,volume=10480
Contributor guide
Research direction
Start with the posted Kapacitor task definition and its DOT output, then compare the 19 points entering alert3 with the 8 points sent to influxdb_out4. Reproduce the stream using the shown TICKscript and determine whether the difference is expected alert behavior or a data-loss bug; done means documenting the cause and the relevant processing semantics.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100