Applying a Downtime with Include ALL Services = YES does not include Host Downtime in the eventstream
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 616
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
As per the title, we noted that the host downtime is not included in the eventstream when all ALL Services is set to yes/true when adding a downtime. Is there a particulare reason why the host object itself is skipped? We require that all services are placed in downtime but the stream is bloated with each individual service and not the actual host.
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 tracing downtime creation with Include ALL Services enabled through the eventstream entry point; the issue does not name a source file or test. Compare the emitted host and service downtime events, then add coverage showing the host object is represented while the requested service downtimes remain correct.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100