Skip to content

Icinga DB: cancel_time in downtime history should not be 0 #9612

@julianbrost

Description

@julianbrost

The following sends a 0 value for cancel_time in the downtime history if the downtime wasn't actually cancelled:
https://github.com/Icinga/icinga2/blob/master/lib/icingadb/icingadb-objects.cpp#L1923

This will then write a 0 timestamp to the corresponding column in the database rather than a NULL value. Icinga 2 should either write null to Redis or omit the key in the JSON altogether if the downtime wasn't cancelled.

refs Icinga/icingadb-web#691

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions