Fixed
Details
Assignee
Alex MayAlex MayReporter
JianYetJianYetHB Grooming Date
Feb 28, 2023HB Backlog Status
Refined BacklogSprint
NoneAffects versions
Priority
Medium
Details
Details
Assignee
Alex May
Alex MayReporter
JianYet
JianYetHB Grooming Date
Feb 28, 2023
HB Backlog Status
Refined Backlog
Sprint
None
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created February 10, 2023 at 9:07 PM
Updated April 6, 2023 at 6:53 PM
Resolved April 6, 2023 at 6:53 PM
Description
From the UI, adding or editing an existing schedule outage for
Threshold checking
- enabling/disabling a package has no effect on the outage entry inthreshd-configuration.xml
although the UI reflects the new status. Others such as Notifications, Polling, Data collection reload their respective configuration upon change and therefore new outage entries are updated accordingly. This is the expected behavior but it’s not the case for Thresholds. When in this state, reloading Threshd manually will revert the changes made since it’s loading the configuration that has not been updated.Workaround
Somehow for some reasons only by deleting a schedule outage from the UI will prompt the outage entries to be updated in
threshd-configuration.xml
.