Dependency with disable_notifications still allows DOWNTIMEEND notification
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 616
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Describe the Bug
A host with a configured dependency still sends a DOWNTIMEEND notification even though disable_notifications = true is set on the dependency.
Example configuration:
apply Dependency "remote-location" to Host {
parent_host_name = "remote-location"
disable_checks = true
disable_notifications = true
assign where "remote" in host.groups
}
Despite notifications being disabled via the dependency, a DOWNTIMEEND notification is still triggered.
To Reproduce
- Configure a host dependency with disable_notifications = true.
- Create a notification that triggers on DOWNTIMEEND.
- Put the dependent host into downtime.
- Let the downtime expire.
Expected Behavior
When disable_notifications = true is set on a dependency, no notifications (including DOWNTIMEEND) should be sent for the dependent host.
Alternatively, it would be helpful to have more granular control over which notification types are suppressed when using dependencies.
Environment
Icinga 2 version: r2.15.1-1
Operating System: Ubuntu 22.04.5 LTS (Jammy Jellyfish)
Enabled features: api, checker, icingadb, influxdb, mainlog, notification
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
No source files or tests are named. Start by reproducing the dependency configuration and downtime-expiry sequence described in the issue, then trace how dependency notification suppression handles DOWNTIMEEND; done means the dependent host sends no notification when disable_notifications is true.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100