It might not be exactly 1.6 MB but it should get to the finished state and be close to 1.6 MB.
Based on the ingress stats you are receiving the data as expected and your task looks to be configured with the right dbrp, so the recording should work. Can you share the exact command you are using to create the recording? On Tuesday, October 18, 2016 at 2:27:27 PM UTC-6, A Sun wrote: > > I was trying to reproduce your results where you mentioned the output size > should be 1.6mb. > > $ kapacitor list recordings $rid > ID Type Status Size Date > 7bd3ced5-5e95-4a67-a0e1-f00860b1af47 stream finished 1.6 MB 04 May 16 > 11:44 MDT > > > On Tue, Oct 18, 2016 at 3:23 PM, Alex Sun <alex...@gmail.com <javascript:> > > wrote: > >> The output is pasted below. The line pertaining to 3d printer example is >> printer.autogen. >> >> >> >> Database Retention Policy Measurement >> Points Received >> _internal monitor cq >> 1910 >> _kapacitor autogen kapacitor >> 1909 >> telegraf autogen disk >> 2624 >> telegraf autogen cpu >> 1312 >> _internal monitor write >> 1910 >> _kapacitor autogen ingress >> 43657 >> _kapacitor autogen runtime >> 1909 >> telegraf autogen processes >> 656 >> printer autogen temperatures >> 864020 >> kapacitor_example autogen cpu >> 387 >> _internal monitor tsm1_engine >> 41415 >> _internal monitor httpd >> 1910 >> telegraf autogen kernel >> 656 >> _internal monitor queryExecutor >> 1910 >> _internal monitor >> tsm1_filestore 41415 >> _internal monitor shard >> 41415 >> _internal monitor tsm1_wal >> 41415 >> _internal monitor runtime >> 1910 >> _internal monitor subscriber >> 8940 >> telegraf autogen mem >> 656 >> _kapacitor autogen nodes >> 18723 >> _kapacitor autogen edges >> 26095 >> telegraf autogen system >> 656 >> telegraf autogen diskio >> 3280 >> _internal monitor database >> 5125 >> telegraf autogen swap >> 656 >> _internal monitor tsm1_cache >> 41415 >> >> On Tue, Oct 18, 2016 at 3:16 PM, <nath...@influxdb.com <javascript:>> >> wrote: >> >>> What is the output of `kapacitor stats ingress`? >>> >>> On Tuesday, October 18, 2016 at 2:11:13 PM UTC-6, A Sun wrote: >>>> >>>> I didn't see any error in the kapacitor.log file about not being able >>>> to write to log files. I tried the telegraf/influxdb/kapacitor cpu_alert >>>> example, which worked. So I think the problem is that the test data >>>> generator wasn't able to write to the recording stream. I always got >>>> "running" but not "finished" status on the recording stream. >>>> >>>> 5d954874-dff8-4a86-adc0-009a011c40f7 stream running 0 B 18 >>>> Oct 16 10:24 CDT >>>> >>>> On Tue, Oct 18, 2016 at 2:56 PM, <nath...@influxdb.com> wrote: >>>> >>>>> Based on the stats from the show output it looks like all three alert >>>>> nodes have produced at least some alerts. Does the directory /tmp/test >>>>> exist? Is it writable by the kapacitord process? Are there any errors in >>>>> the logs about not being able to write to the log files? >>>>> >>>>> >>>>> >>>>> On Tuesday, October 18, 2016 at 9:43:19 AM UTC-6, A Sun wrote: >>>>>> >>>>>> Hi, I'm new to kapacitor. I tried to follow the steps in custom >>>>>> anomaly detection example ( >>>>>> https://docs.influxdata.com/kapacitor/v1.0/examples/anomaly_detection/) >>>>>> >>>>>> >>>>>> However, I don't see any alert log files after running the task. >>>>>> >>>>>> The data stream seems to be empty after running the test data >>>>>> generator, >>>>>> >>>>>> >>>>>> ID Type Status Size >>>>>> Date >>>>>> 8724ca17-7ff5-4694-8b66-aae14d4be7f4 stream running 0 B >>>>>> 18 Oct 16 10:28 CDT >>>>>> >>>>>> >>>>>> >>>>>> Here's output from "kapacitor show print_temps". It seems some events >>>>>> were processed but no alerts were logged. >>>>>> >>>>>> { >>>>>> "link": { >>>>>> "rel": "self", >>>>>> "href": "/kapacitor/v1/tasks/print_temps" >>>>>> }, >>>>>> "id": "print_temps", >>>>>> "template-id": "", >>>>>> "type": "stream", >>>>>> "dbrps": [ >>>>>> { >>>>>> "db": "printer", >>>>>> "rp": "autogen" >>>>>> } >>>>>> ], >>>>>> "script": "// This TICKscript monitors the three temperatures for >>>>>> a 3d printing job,\n// and triggers alerts if the temperatures start to >>>>>> experience abnormal behavior.\n\n// Define our desired significance >>>>>> level.\nvar alpha = 0.001\n\n// Select the temperatures >>>>>> measurements\nvar >>>>>> data = stream\n |from()\n .measurement('temperatures')\n >>>>>> |window()\n .period(5m)\n .every(5m)\n\ndata\n // Run >>>>>> our >>>>>> tTest UDF on the hotend temperature\n @tTest()\n // specify >>>>>> the >>>>>> hotend field\n .field('hotend')\n // Keep a 1h rolling >>>>>> window\n .size(3600)\n // pass in the alpha value\n >>>>>> .alpha(alpha)\n |alert()\n .id('hotend')\n >>>>>> .crit(lambda: >>>>>> \"pvalue\" \u003c alpha)\n >>>>>> .log('/tmp/test/hotend_failure.log')\n\n// Do the same for the bed and >>>>>> air >>>>>> temperature.\ndata\n @tTest()\n .field('bed')\n >>>>>> .size(3600)\n .alpha(alpha)\n |alert()\n .id('bed')\n >>>>>> >>>>>> .crit(lambda: \"pvalue\" \u003c alpha)\n >>>>>> .log('/tmp/test/bed_failure.log')\n\ndata\n @tTest()\n >>>>>> .field('air')\n .size(3600)\n .alpha(alpha)\n >>>>>> |alert()\n >>>>>> .id('air')\n .crit(lambda: \"pvalue\" \u003c alpha)\n >>>>>> >>>>>> .log('/tmp/test/air_failure.log')\n", >>>>>> "vars": {}, >>>>>> "dot": "digraph print_temps {\ngraph [throughput=\"0.00 >>>>>> points/s\"];\n\nstream0 [avg_exec_time_ns=\"0\" ];\nstream0 -\u003e >>>>>> from1 >>>>>> [processed=\"86402\"];\n\nfrom1 [avg_exec_time_ns=\"225.328µs\" >>>>>> ];\nfrom1 >>>>>> -\u003e window2 [processed=\"86402\"];\n\nwindow2 >>>>>> [avg_exec_time_ns=\"160.576µs\" ];\nwindow2 -\u003e tTest7 >>>>>> [processed=\"288\"];\nwindow2 -\u003e tTest5 >>>>>> [processed=\"288\"];\nwindow2 >>>>>> -\u003e tTest3 [processed=\"288\"];\n\ntTest7 >>>>>> [avg_exec_time_ns=\"196.929082ms\" ];\ntTest7 -\u003e alert8 >>>>>> [processed=\"214\"];\n\nalert8 [alerts_triggered=\"9\" >>>>>> avg_exec_time_ns=\"9.05µs\" crits_triggered=\"6\" infos_triggered=\"0\" >>>>>> oks_triggered=\"3\" warns_triggered=\"0\" ];\n\ntTest5 >>>>>> [avg_exec_time_ns=\"179.950039ms\" ];\ntTest5 -\u003e alert6 >>>>>> [processed=\"211\"];\n\nalert6 [alerts_triggered=\"4\" >>>>>> avg_exec_time_ns=\"23.838µs\" crits_triggered=\"3\" >>>>>> infos_triggered=\"0\" >>>>>> oks_triggered=\"1\" warns_triggered=\"0\" ];\n\ntTest3 >>>>>> [avg_exec_time_ns=\"114.502568ms\" ];\ntTest3 -\u003e alert4 >>>>>> [processed=\"214\"];\n\nalert4 [alerts_triggered=\"4\" >>>>>> avg_exec_time_ns=\"43.406µs\" crits_triggered=\"2\" >>>>>> infos_triggered=\"0\" >>>>>> oks_triggered=\"2\" warns_triggered=\"0\" ];\n}", >>>>>> "status": "enabled", >>>>>> "executing": true, >>>>>> "error": "", >>>>>> "stats": { >>>>>> "task-stats": { >>>>>> "throughput": 0 >>>>>> }, >>>>>> "node-stats": { >>>>>> "alert4": { >>>>>> "alerts_triggered": 4, >>>>>> "avg_exec_time_ns": 43406, >>>>>> "collected": 214, >>>>>> "crits_triggered": 2, >>>>>> "emitted": 0, >>>>>> "infos_triggered": 0, >>>>>> "oks_triggered": 2, >>>>>> "warns_triggered": 0 >>>>>> }, >>>>>> "alert6": { >>>>>> "alerts_triggered": 4, >>>>>> "avg_exec_time_ns": 23838, >>>>>> "collected": 211, >>>>>> "crits_triggered": 3, >>>>>> "emitted": 0, >>>>>> "infos_triggered": 0, >>>>>> "oks_triggered": 1, >>>>>> "warns_triggered": 0 >>>>>> }, >>>>>> "alert8": { >>>>>> "alerts_triggered": 9, >>>>>> "avg_exec_time_ns": 9050, >>>>>> "collected": 214, >>>>>> "crits_triggered": 6, >>>>>> "emitted": 0, >>>>>> "infos_triggered": 0, >>>>>> "oks_triggered": 3, >>>>>> "warns_triggered": 0 >>>>>> }, >>>>>> "from1": { >>>>>> "avg_exec_time_ns": 225328, >>>>>> "collected": 86402, >>>>>> "emitted": 86402 >>>>>> }, >>>>>> "stream0": { >>>>>> "avg_exec_time_ns": 0, >>>>>> "collected": 86402, >>>>>> "emitted": 86402 >>>>>> }, >>>>>> "tTest3": { >>>>>> "avg_exec_time_ns": 114502568, >>>>>> "collected": 220, >>>>>> "emitted": 214 >>>>>> }, >>>>>> "tTest5": { >>>>>> "avg_exec_time_ns": 179950039, >>>>>> "collected": 217, >>>>>> "emitted": 211 >>>>>> }, >>>>>> "tTest7": { >>>>>> "avg_exec_time_ns": 196929082, >>>>>> "collected": 221, >>>>>> "emitted": 214 >>>>>> }, >>>>>> "window2": { >>>>>> "avg_exec_time_ns": 160576, >>>>>> "collected": 86402, >>>>>> "emitted": 864 >>>>>> } >>>>>> } >>>>>> }, >>>>>> "created": "2016-10-17T21:33:16.176203257-05:00", >>>>>> "modified": "2016-10-18T10:28:00.685262934-05:00", >>>>>> "last-enabled": "2016-10-18T10:28:00.685262934-05:00" >>>>>> } >>>>>> >>>>> -- >>>>> Remember to include the version number! >>>>> --- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "InfluxData" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/influxdb/BZwNlTqSPQQ/unsubscribe. >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> influxdb+u...@googlegroups.com. >>>>> To post to this group, send email to infl...@googlegroups.com. >>>>> 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/dedf482a-c021-4496-a3fc-9ce34f713ff5%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/influxdb/dedf482a-c021-4496-a3fc-9ce34f713ff5%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> Remember to include the version number! >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "InfluxData" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/influxdb/BZwNlTqSPQQ/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> influxdb+u...@googlegroups.com <javascript:>. >>> To post to this group, send email to infl...@googlegroups.com >>> <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/a85dfa4a-6ff7-4fd8-b19d-94ec899199f7%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/influxdb/a85dfa4a-6ff7-4fd8-b19d-94ec899199f7%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+unsubscr...@googlegroups.com. To post to this group, send email to influxdb@googlegroups.com. 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/75b80a1f-e280-43fe-bed5-bfe617ddebf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
