Subscriptions are unrelated to querying. The logs lines you see are because the old subscriptions still exist. Use the DROP SUBSCRIPTION ... query to remove them.
On Friday, November 4, 2016 at 9:20:02 AM UTC-6, [email protected] wrote: > > On Thursday, November 3, 2016 at 2:36:04 PM UTC-4, [email protected] > wrote: > > I am trying to setup high availability setup of influxdb using influxdb > relays.So telegraf clients send data to both host1 and host2 via influxdb > relay. > > > > telegraf --> Loadbalancer-->influxdbrelay --> influxdb@host1 and @host2 > > > > I want kapacitor to generate alert from influxdb@host1 if its available > and for some reason if host1 goes down i want it to query influxdb@host2. > Is it possible? > > > > Should i be pointing kapacitor to loadbalancer infront of influxdbrelays > or directly as given below in kapacitor.conf==> > > > > [[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 = "xyzhost" > > urls = ["http://host1:8086","http://host2:8086";] > > > > Or should it be > > urls = ["http://loadbalancer hostname:port"] > > > > If you have above influxdb configuration with host1, host2 in urls list, > will kapacitor subscribe to both host1 and host2 and query both. Or will it > first query host1 and if it fails then queries host2? > > > > If i subsequently define a task that generates alert for high cpu will > it generate from host1 or host2? > > If i unsubscribe how am i going to query via loadbalancer? > I tried : > > [[influxdb]] > > # Turn off all subscriptions > disable-subscriptions = true > > > but i still see in /var/log/kapacitor/kapacitor.log following messages > that tells me the subscription is still happening: > > [noauth] 2016/11/04 15:18:20 W! using noauth auth backend. Faked > authentication for subscription user token > [httpd] 10.93.73.184 - ~subscriber [04/Nov/2016:15:18:20 +0000] "POST > /write?consistency=&db=_internal&precision=ns&rp=monitor HTTP/1.1" 204 0 > "-" "InfluxDBClient" eb26ec48-a2a1-11e6-8020-000000000000 858 > [noauth] 2016/11/04 15:18:30 W! using noauth auth backend. Faked > authentication for subscription user token > [httpd] 10.93.73.184 - ~subscriber [04/Nov/2016:15:18:30 +0000] "POST > /write?consistency=&db=_internal&precision=ns&rp=monitor HTTP/1.1" 204 0 > "-" "InfluxDBClient" f11cdfca-a2a1-11e6-8021-000000000000 877 > > -- 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/bcf168dc-8cd7-4aa2-9838-b2bcdce71c99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
