The primary purpose of Maintenance Windows in DX Operational Observability is to schedule periods for preventive maintenance activities that could otherwise cause service disruptions.
In the context of alarm management, applying a maintenance window serves several distinct functions:
If O2 allows a ticket on an alarm that is scheduled to be in maintenance, then from my perspective, it does not meet the above scope of Alarm analytics and Maintenance windows as described.
We are see alarms coming in trigger Ticket for an AlarmID that has been targeted to be ignored, but because the Device is not active the AlarmID is ticked. Why is this happening?
DX O2 SaaS
Entity filtering can be done either by directly selecting from the list or by providing a regex pattern. Internally, these are identified by their external ids. We can filter on any TAS attribute, but currently, only these 6 are exposed.
We do have an enhancement to add more attributes for O2 when filtering entities, currently in the evaluation phase.