[Incident 418dfe03-fd4d-4910-a5b0-09151c13f000] Azure Monitor 'test-alert' fired on App Service 'sredemo-web' (region: unknown)

[TimoSalomaki]

Incident overview

• Incident ID: 418dfe03-fd4d-4910-a5b0-09151c13f000
• First seen (UTC): 2025-12-18T02:56:13.4341133Z
• Detection source: Azure Monitor (metric alert)
• Severity: Sev1
• Impacted service/app: Azure App Service 'sredemo-web'
• Impacted endpoints/users: Unknown (please provide if any customer-facing impact observed)

Environment

• Subscription ID: 7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf
• Resource Group: rg-sredemo
• Resource ID: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourcegroups/rg-sredemo/providers/microsoft.web/sites/sredemo-web
• Region: Unknown (please confirm)
• Service tier/SKU: Unknown (please confirm)
• Alert Rule: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourceGroups/rg-sredemo/providers/microsoft.insights/metricAlerts/test-alert

Symptoms and errors

• Alert name: test-alert
• Description: (empty in alert payload)
• Error messages/correlation IDs: Not present
• Monitor condition: Fired

Change/Activity summary (last 24h)

• No Azure Activity Logs found for this resource or dependencies in the last 24 hours.

Metrics snapshot (last 2 hours, UTC window: now-2h to now)

• Requests (req/min): Sparse minimal traffic, typically 0–1 req/min, no sustained spikes.
• HTTP 5xx (count/min): 0 across the full window.
• MemoryWorkingSet: Stable in the ~176–185 MiB range; gradual, small increases/variations but no extreme growth.
• AverageResponseTime: When sampled, averages ~7–26 ms; samples are sparse due to low traffic.

Reproduction steps

• None identified; alert fired at 2025-12-18T02:56:13Z; current metrics show healthy behavior over the last 2 hours.

Attempted mitigations

• None performed; platform-side signals appear healthy at this time.

Proposed next steps for engineering

1. Confirm environment details (region, SKU/tier, slots) and whether any customer impact was observed.
2. Review the Azure Monitor alert rule 'test-alert' configuration and thresholds to verify correctness and reduce false positives.
3. Validate metrics behind the alert (namespace Microsoft.Web/sites) and ensure the correct aggregation/dimension is targeted.
4. Inspect App Service diagnostics (App Service Diagnostics, Kudu logs) for any intermittent errors around 2025-12-18T02:56Z.
5. Check deployment history or configuration changes near the alert first-seen time and prior hours; share any change timeline.
6. If applicable, add additional signals (Http4xx rate, CPU Time/Percentage, Instance health) to the alert or dashboard to improve detection fidelity.

References

• Alert ID: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourcegroups/rg-sredemo/providers/microsoft.web/sites/sredemo-web/providers/Microsoft.AlertsManagement/alerts/418dfe03-fd4d-4910-a5b0-09151c13f000
• Alert Rule resource: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourceGroups/rg-sredemo/providers/microsoft.insights/metricAlerts/test-alert

Please acknowledge and provide ETA for triage. Attach any additional logs, correlation IDs, or dashboards relevant to this incident.

This issue was created by sredemo--062602c3
Tracked by the SRE agent here