Maintenance Window based on Service didn't work as expected

Products

• DX SaaS
• DX Operational Observability

Issue/Introduction

Maintenance Window based on a Service that should have covered a number of Alarms didn't work as expected

Environment

DX O2

Cause

1. We found that Service definition is based on an attribute, this means that the Service will be automatically updated if new entities have the attribute.

2. From the TAS history we found that entity for the problematic alarm was ingested during the maintenance window.  Since at the start of the schedule, the entity was not available, it was not marked for maintenance. Only those entities that are available at the start will be put to maintenance during the active window.

TIP: You can check for the entity history by using the below REST API call , you can use epoch converter tool to generate the start and end time for the troubleshooting.

POST <apmservices-gateway>/tas/graph/queryHistory

{
    "filter":
    {
        "op": "VERTEX",
        "externalId":
        [
            "<replace this with your external ID"
        ]
    },
    "startTime": <epoch starttime>,
    "endTime": <epoch endtime>
}

Resolution

Make sure to understand the "Maintenance requirements" for Services when dynamics update based on attribute(s) is enabled.

Additional Information

Techdocs DX O2 - Create Maintenance Windows