This repository was archived by the owner on Feb 13, 2025. It is now read-only.

Description
Hi all,
we're running 785bf4e and I just introduced slack based notification into our Bosun configuration. Unfortunately, the next action is not executed as expected after a timeout of 15 min -- in case of a warning -- or immediately -- in case of a critical event. Below is my current configuration. Is this a bug or is there an error in my config?
notification default {
email = infrastructure-hosting-team@XXXX
next = default
timeout = 6h
}
notification slack.warn {
post = https://hooks.slack.com/services/XXXX
body = payload={"username": "Bosun Cluster B", "channel": "#alerts-clusterb", "text": {{.|json}}, "icon_url": "https://raw.githubusercontent.com/bosun-monitor/bosun/master/cmd/bosun/web/static/img/tsaf-logo-mark.png"}
next = default
timeout = 15m
}
notification slack.crit {
post = https://hooks.slack.com/services/XXXX
body = payload={"username": "Bosun Cluster B", "channel": "#alerts-clusterb", "text": {{.|json}}, "icon_url": "https://raw.githubusercontent.com/bosun-monitor/bosun/master/cmd/bosun/web/static/img/tsaf-logo-mark.png"}
next = default
}
Thanks in advance,
cheers,
Lukas