influxdata / influxdata/kapacitor
Alert Generate issue
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Hi Team,
We are using kapacitor-1.5.3-1.x86_64 and chronograf-1.7.14-1.x86_64 and influxdb-1.7.6-1.x86_64.
Kapacitor and Chronograf are running on one server and InfluxDB is running on another server.
I can see all Tables and other details on Chronograf under "Build Alert Rule" but unable to generate Alert.
I have added InfluxDB server IP in kapacitor config file.
Please help to know, why no alert is generating through kapacitor ?
is there any configuration required because InfluxDB is running in another server.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Kapacitor configuration and the Chronograf "Build Alert Rule" workflow described in the report. Verify how Kapacitor connects to the remote InfluxDB instance and determine what configuration or connectivity failure prevents alert generation; done means an alert can be created and generated across the two servers.
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
- 25/100