Icinga DB: send all info needed to re-construct history event IDs
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
TLDR; Icinga 2 uses the cr.execution_end as part of the history event SHA1 IDs, which only exists within Icinga 2 itself, making it impossible to reconstruct the history event ID with the information received either from the icinga:history:stream:state or icinga:runtime:state streams. Icinga DB should send all the information needed to construct that as part of the icinga:runtime:state stream, which Icinga DB (Go) can make use of to reconstruct and correlate Icinga Notifications notification histories with the actual Icinga DB state change histories.
See https://github.com/Icinga/icingadb/issues/1112#issuecomment-5250231950 for the long version of this issue.
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 the icinga:runtime:state and icinga:history:stream:state entry points, then review how cr.execution_end contributes to history event SHA1 IDs. Use the linked Icinga DB discussion for the required correlation context. Done means the runtime state stream exposes all information needed to reconstruct and correlate the history event IDs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100