Add attributes maintenance window
search cancel

Add attributes maintenance window

book

Article ID: 437915

calendar_today

Updated On:

Products

DX SaaS

Issue/Introduction

 

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:

  • Suspension of Monitoring: During the maintenance period, all monitoring and metric calculations for the selected alarms, entities, groups, or services are stopped, although you can still monitor their overall health and status.
  • Alarm and Notification Suppression: Except for Anomaly alarms, all other alarms continue to be ingested and their lifecycles remain unchanged. However, alarm notifications are suppressed to prevent false alerts and noise while the maintenance work is being performed.
  • Automatic Status Tagging: Both existing alarms and any newly generated alarms for the specified entity automatically go "under maintenance" when the window begins, and they return to normal when the window ends.
  • Visibility and Filtering: Alarms under maintenance are flagged with a specific Maintenance icon in the All Alarms view. This allows operators to easily hide them (using the Maintenance:false filter) or view only maintenance alarms (using the Maintenance:true filter).

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?

 

Environment

DX O2 SaaS

Resolution

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.