influxdata / influxdata/kapacitor
Kapacitor header alert to RabbitMQ
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Hello everybody,
I'm trying to create an MQTT alert on kapacitor writing to a queue on RabbitMQ. I configured kapacitor.config like this:
[[mqtt]]
enabled = true
name = "localhost"
default = true
url = "tcp://localhost:1883"
[[mqtt]]
enabled = true
name = "alerts-broker"
default = false
url = "ssl://123.45.67.89:1883"
ssl-ca = "/etc/kapacitor/ca.pem"
ssl-cert = "/etc/kapacitor/cert.pem"
ssl-key = "/etc/kapacitor/key.pem"
client-id = "alerts-broker"
username = "mqadmin"
password = "mqadminpassword"
and a tickScript like this:
stream
|from()
.measurement('cpu')
|alert()
.crit(lambda: "usage_idle" < 45)
.message('Tom Test OK')
.topic('cpu')
But it doesn't work. Can you help me?
Tommaso
Contributor guide
Research direction
Start by reviewing the MQTT sections in kapacitor.config alongside the alert() topic in the tickScript. Trace how the alert is expected to reach the RabbitMQ queue and document a reproducible configuration or implementation path; done means the CPU alert is delivered successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rabbitmq
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100