Do you get the error for all points or just some of them? If its just some
of them that could explain it. While the field key may exist in the data
set its still possible that a single points doesn't have the field.
In this case you can use the default node to set the field if its missing,
thus avoiding the error in the log.
stream
|from()
.measurement('net')
|default()
.field('tcp_inerrors', 0)
|where(lambda: "tcp_inerrors" > 0)
Looks like you are using Telegraf. We should probably look into why points
can arrive without the field.
On Wednesday, June 15, 2016 at 5:21:46 PM UTC-6, Moti Levy wrote:
>
> I can't seem to get Kapacitor to work with specific fields for some reason.
>
> Example tick :
>
>>
>> ID: global-net_tcp_inerrs
>> Error:
>> Type: stream
>> Status: enabled
>> Executing: true
>> Created: 15 Jun 16 21:22 UTC
>> Modified: 15 Jun 16 23:17 UTC
>> LastEnabled: 15 Jun 16 23:17 UTC
>> Databases Retention Policies: ["telegraf"."default"]
>> TICKscript:
>> stream
>> |from()
>> .measurement('net')
>> .where(lambda: "tcp_inerrs" > 0)
>>
>> DOT:
>> digraph global-net_tcp_inerrs {
>> graph [throughput="0.00 points/s"];
>> stream0 [avg_exec_time_ns="0" ];
>> stream0 -> from1 [processed="566"];
>> from1 [avg_exec_time_ns="56.09µs" ];
>> }
>
>
> results in :
>
> error while evaluating WHERE expression: no field or tag exists for
>> tcp_inerrs
>
>
> Yet the field is there :(
>
> > show field keys from net
>> name: net
>> ---------
>> fieldKey
>> bytes_recv
>> bytes_sent
>> drop_in
>> drop_out
>> err_in
>> err_out
>> icmp_inaddrmaskreps
>> icmp_inaddrmasks
>> icmp_incsumerrors
>> icmp_indestunreachs
>> icmp_inechoreps
>> icmp_inechos
>> icmp_inerrors
>> icmp_inmsgs
>> icmp_inparmprobs
>> icmp_inredirects
>> icmp_insrcquenchs
>> icmp_intimeexcds
>> icmp_intimestampreps
>> icmp_intimestamps
>> icmp_outaddrmaskreps
>> icmp_outaddrmasks
>> icmp_outdestunreachs
>> icmp_outechoreps
>> icmp_outechos
>> icmp_outerrors
>> icmp_outmsgs
>> icmp_outparmprobs
>> icmp_outredirects
>> icmp_outsrcquenchs
>> icmp_outtimeexcds
>> icmp_outtimestampreps
>> icmp_outtimestamps
>> icmpmsg_intype0
>> icmpmsg_intype11
>> icmpmsg_intype3
>> icmpmsg_intype8
>> icmpmsg_outtype0
>> icmpmsg_outtype3
>> icmpmsg_outtype5
>> icmpmsg_outtype8
>> ip_defaultttl
>> ip_forwarding
>> ip_forwdatagrams
>> ip_fragcreates
>> ip_fragfails
>> ip_fragoks
>> ip_inaddrerrors
>> ip_indelivers
>> ip_indiscards
>> ip_inhdrerrors
>> ip_inreceives
>> ip_inunknownprotos
>> ip_outdiscards
>> ip_outnoroutes
>> ip_outrequests
>> ip_reasmfails
>> ip_reasmoks
>> ip_reasmreqds
>> ip_reasmtimeout
>> packets_recv
>> packets_sent
>> tcp_activeopens
>> tcp_attemptfails
>> tcp_currestab
>> tcp_estabresets
>> tcp_incsumerrors
>> tcp_inerrs
>> tcp_insegs
>> tcp_maxconn
>> tcp_outrsts
>> tcp_outsegs
>> tcp_passiveopens
>> tcp_retranssegs
>> tcp_rtoalgorithm
>> tcp_rtomax
>> tcp_rtomin
>> udp_ignoredmulti
>> udp_incsumerrors
>> udp_indatagrams
>> udp_inerrors
>> udp_noports
>> udp_outdatagrams
>> udp_rcvbuferrors
>> udp_sndbuferrors
>> udplite_ignoredmulti
>> udplite_incsumerrors
>> udplite_indatagrams
>> udplite_inerrors
>> udplite_noports
>> udplite_outdatagrams
>> udplite_rcvbuferrors
>> udplite_sndbuferrors
>
>
> Anything I am missing ?
>
> Moti
>
>
>
>
--
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/7ac7706e-fae5-4f8b-944d-dd88c7dd7403%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
