influxdata / influxdata/kapacitor
kapacitor configuration with influx db cluster
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Hi,
I would like to double check with you since I did not found anything about this issue in documentation.
We have influxdb cluster with the following configuration:
ELB infrastructure-> 5 influx db that gets only infrastructure metrics.
ELB APP - > 5 influx db that gets only app metrics.
the elb is doing load balancer.
I have installed kapacitor on another server and when I start the kapacitor service the subscription does not created automatically.
I read a few cases like that
https://github.com/influxdata/kapacitor/issues/1028
https://groups.google.com/forum/#!searchin/influxdb/relay$20subscriptions$20kapacitor%7Csort:relevance/influxdb/yImf4Uok2T4/xvKdvIC2BgAJ
and I am not sure which subscription do i have to create and where?
should I create subscription on each influx db manually? or only on one of them?
Thanks,
Noy.
Contributor guide
Research direction
Start by reviewing the Kapacitor configuration and subscription behavior described in the issue, then read the linked Kapacitor issue 1028 and the referenced InfluxDB discussion. Determine whether subscriptions should be created automatically and whether they belong on each InfluxDB node or only one; document the confirmed setup and expected behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100