Influxdb Gurus! I have following questions regarding Kapacitor which will help me appropriately decide its implementation in my env:
1) In TICK stack setup where kapacitor subscribes to influxdb for getting data stream, how many kapacitors can subscribe to one influxdb server? 2) when kapacitor subscribes to influxdb, is it one time job for influxdb to register the requesting kapacitor and start streaming data to it or does it have to actively manage kapacitor end point affecting its performance in some way? 3) If i give names of primary and secondary influxdb servers in kapacitor.conf file: [[influxdb]] # Connect to an InfluxDB cluster # Kapacitor can subscribe, query and write to this cluster. # Using InfluxDB is not required and can be disabled. enabled = true default = true name = "localhost" urls = ["http://primaryinfluxdb:8086","http://secondaryinfluxdb:8086";] then will kapacitor get data stream from both primary and secondary at the same time or will it try the second only if first one fails? 4) Where is this streamed data stored in kapacitor (RAM ?). What happens to data in memory when kapacitor is restarted? Is it flushed to disk? If i have a tick script that alerts on mean value of last 24hr cpu usage, if data is in memory then how will kapacitor calculate mean if it gets restarted? -- 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 [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/30789f3d-354e-4e6f-8635-1e69c49e5c6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
