kapacitor stream data entries in parts

Nobody has claimed this yet.

I am working on making an alert for net using the example in this project. However I was getting two errors: " cannot apply derivative to type " and "cannot perform derivative elapsed time was 0." After some monkeying, it looks like from the logs that there are two entries for the same data point. One entry has half of the information and the other has the rest. When I query the influx there is only one data point, any idea why kapacitor is getting it in two parts?

these are the log entries

> [net_alert:log2] 2017/02/09 23:59:00 I! {"Name":"net","Database":"telegraf","RetentionPolicy":"autogen", ...Fields":{"bytes_recv":331511714,"bytes_sent":1050173914,"drop_in":0,"drop_out":0,"err_in":0,"err_out":0,"pack
ets_recv":1821862,"packets_sent":2538422},"Time":"2017-02-09T23:59:00Z"}

> [net_alert:log2] 2017/02/09 23:59:00 I! {"Name":"net","Database":"telegraf","RetentionPolicy":"autogen", ...Fields":{"icmp_inaddrmaskreps":0,"icmp_inaddrmasks":0,"icmp_incsumerrors":0,"icmp_indestunreachs":114,"icmp_inechoreps":0,"icmp_inechos":0,"icmp_inerrors":56,"icmp_inmsgs":114,"icmp_inparmprobs":0,"icmp_inredirects":0,"icmp_insrcquenchs":0,"icmp_intimeexcds":0,"icmp_intimestampreps":0,"icmp_intimestamps":0,"icmp_outaddrmaskreps":0,"icmp_outaddrmasks":0,"icmp_outdestunreachs":114,"icmp_outechoreps":0,"icmp_outechos":0,"icmp_outerrors":0,"icmp_outmsgs":114,"icmp_outparmprobs":0,"icmp_outredirects":0,"icmp_outsrcquenchs":0,"icmp_outtimeexcds":0,"icmp_outtimestampreps":0,"icmp_outtimestamps":0,"icmpmsg_intype3":114,"icmpmsg_outtype3":114,"ip_defaultttl":255,"ip_forwarding":2,"ip_forwdatagrams":0,"ip_fragcreates":0,"ip_fragfails":0,"ip_fragoks":0,"ip_inaddrerrors":2,"ip_indelivers":5056064,"ip_indiscards":0,"ip_inhdrerrors":0,"ip_inreceives":5056066,"ip_inunknownprotos":0,"ip_outdiscards":0,"ip_outnoroutes":0,"ip_outrequests":5747342,"ip_reasmfails":0,"ip_reasmoks":0,"ip_reasmreqds":0,"ip_reasmtimeout":0,"tcp_activeopens":270090,"tcp_attemptfails":90,"tcp_currestab":4,"tcp_estabresets":5,"tcp_incsumerrors":0,"tcp_inerrs":6,"tcp_insegs":4877963,"tcp_maxconn":-1,"tcp_outrsts":101761,"tcp_outsegs":5496892,"tcp_passiveopens":89667,"tcp_retranssegs":72169,"tcp_rtoalgorithm":1,"tcp_rtomax":120000,"tcp_rtomin":200,"udp_ignoredmulti":0,"udp_incsumerrors":0,"udp_indatagrams":177985,"udp_inerrors":0,"udp_noports":2,"udp_outdatagrams":178384,"udp_rcvbuferrors":0,"udp_sndbuferrors":0,"udplite_ignoredmulti":0,"udplite_incsumerrors":0,"udplite_indatagrams":0,"udplite_inerrors":0,"udplite_noports":0,"udplite_outdatagrams":0,"udplite_rcvbuferrors":0,"udplite_sndbuferrors":0},"Time":"2017-02-09T23:59:00Z"}

No source file, test, or entry point is identified in the issue. Reproduce the reported net stream with the two log entries and inspect how points reach derivative processing; done means one data point is handled as a complete entry without the reported nil or zero-elapsed-time errors.

Written by the indexing model from the issue text.