influxdata / influxdata/kapacitor

Failed to send Alert to Alerta service

Open
#2,671 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

Hello All!

I found a weird bug . when I try to configure kapacitor with Chronograf and influx db, everything works correctly I can send alerts on Slack or Alerta. So far soo good. When I stopped Chronograf service which contains the settings property i faced a issue .
In kapacitor i can see in the logs :

`
ts=2022-01-17T14:52:35.501+01:00 lvl=error msg="failed to send event to Alerta" service=alerta task=Application-services-check err="service is not enabled"
`
in other words how to tell kapacitor to play the configuration present /etc/kapacitor/kapacitor.conf and not the settings in chronoaf DB.
I have the impression that this one is overloaded in influxdb

Seems pretty confuse by the way..

I have succesfully enable my task like below:

kapacitor list tasks
`ID Type Status Executing Databases and Retention Policies`
`Application-services-check stream enabled true ["sys_metrics"."one_month"]`

i have also re enable the service .
`
kapacitor enable tasks Application-services-check
`

Did i miss something ?

Contributor guide

Open the contributing guide

Research direction

Start with /etc/kapacitor/kapacitor.conf and the logged “service is not enabled” error, then reproduce the issue by stopping Chronograf while the Application-services-check task is enabled. Compare the configuration sources and verify that Kapacitor can send an Alerta event using its configuration file without Chronograf running.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.