1. No software limit, but it will be limited by available resources. 2. Taking things to the extreme the best case is one task that consumes all the data and does all the work, as there will be less overhead etc of managing multiple tasks. That said significant effort has gone into making sure that each new task does not add too much overhead. I would recommend using tasks in a way that makes logical organizational sense first, which probably means many tasks. Then if you do run into performance issues, let's first see if we can fix them within Kapacitor, then as a last resort would I start merging tasks into more complex tasks. 3. Templates are just an ease of use tool and make no difference. 4. Currently when you update a script all state about that task is lost. Specifically for the alert this means they can be left in a triggering state :(. We are working to fix this soon as part of a new alerting system.
As for the docs, they read like reference docs at the moment and so some of the higher level concepts and ideas are missing, but we are slowly tackling those kinds of docs too :) On Wednesday, November 9, 2016 at 3:08:26 AM UTC-7, Julien Ammous wrote: > > Hi, > I have a few question considering how scripts are handled: > 1. is there any limit on the number of scripts kapacitor can handle ? > > 2. is it better to aim for more complex scripts or is it fine to have 2 or > 3 running in parallel performance wise ? > > 3. are templates based scripts using less resources ? more efficient ? or > is it just a ease of use tool and it make no differences below ? > > 4. What happen when you update a script, let's say most of it did not > change but I added an output, if alarms were up before the update will > kapacitor remembers it ? > How are scripts linked to the alert they raised and what can "break" this > link ? I ask this because in most if not all cases when I update a script I > want it to keep tracks of any alert raised before. > > > I tried to find clues on these in the documentation (which is really well > done by the way :) ) but could not find the answers I was looking for. > > -- 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/736f8f2a-0820-4062-aa88-530ad1e36fd8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
