InfluxData's Q&A Session for Oct 20: Intro to Kapacitor for Alerting and Anomaly Detection

Navigate to:

We have posted the video archive for the Oct 13: Intro to Telegraf and the Plugin Ecosystem and the following is a recap of the Q&A session during the training.

Q: What determines choosing batch or stream?

A: Choosing batch vs stream depends on how you would like to process the data. Batching is the equivalent of using InfluxDB’s “GROUP BY” function, where data is segmented into time bound buckets. Streaming would be for processing data in real-time.

Q: Besides the video, will the deck Jack used be posted somewhere?

A: Yes. We will be uploading the all the slides on SlideShare shortly.

Q:Would be cool then to have the kapacitor cli to be able to read the first line of a tick script, like the comment you describe. sort of like a #!/bin/bash…

A: That would be a useful feature. Feel free to open a feature request on github!

Q: Can you talk about naming variable naming conventions? In an earlier part of the demo you accessed a “value” variable. HOw does that correlate to the fields of a batch query. I’ve also seen examples that reference “sum” or “identifier.sum”

A: I don’t think we have a doc on variable naming for TICK scripts so there are no conventions per se. The fields referenced, like ““value””, are usually defined from the InfluxDB/source data.

Q: Why did you create another DSL? Why you didn’t use any old script language?

A: Not sure if I’m qualified to answer that question, you may want to ask Nathaniel on the mailing list. From my understanding, there’s no canonical DAG syntax and we wanted something that integrated very well with influxdb.

Please make sure you sign up for our next free training session on ”Getting Started with the TICK stack and InfluxDB Fundamentals” webinar on 10/27