[Incident c27e686c-52e0-4af8-a7d1-f24e7944f000] Azure Monitor alert 'test-alert' fired on sredemo-web (region: unknown)

[TimoSalomaki]

Incident overview

• Incident ID: c27e686c-52e0-4af8-a7d1-f24e7944f000
• First seen (UTC): 2025-11-13T06:46:48Z
• Detection source: Azure Monitor metric alert (rule: test-alert)
• Severity: Sev1
• Monitor condition: Fired
• Impacted endpoints/users: Unknown (please provide)

Environment

• Subscription ID: 7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf
• Resource Group: rg-sredemo
• Resource: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourceGroups/rg-sredemo/providers/Microsoft.Web/sites/sredemo-web
• Service: Azure App Service (sites)
• Region: Unknown (not present in alert payload)
• Tier/SKU: Unknown (please provide)

Symptoms and errors

• Alert name: test-alert
• Description: (empty in alert)
• Exact errors/correlation IDs: Not provided in alert; none observed in platform metrics (Http5xx = 0 over last 2h)

Recent changes/activity (last 24h)

• No Azure Activity Logs found for the resource or its dependencies in the last 24 hours around the alert time.

Metrics snapshot (last 2 hours, UTC now: 2025-11-30T19:55:22Z)

• Requests: near-zero traffic with intermittent single requests; no surge observed.
• Http5xx: consistently 0 across the 2-hour window.
• AverageResponseTime: mostly ~7–8ms with occasional spikes: ~26ms at 18:29, ~25ms at 18:59, ~16ms at 19:05, ~33ms at 19:10, and a notable outlier ~455ms at 19:40.
• MemoryWorkingSet: stable around 336–346 MiB with a gradual increase then steady state; no signs of memory pressure.
• InstanceCount: not explicitly queried; metric available—please confirm scale/instance count.

Reproduction steps

• Unknown. No clear customer-facing symptoms; alert may be misconfigured or a test rule. Please confirm alert criteria and whether this was a test.

Attempted mitigations

• None applied; platform-side health appears normal and no recent changes detected.

Proposed next steps for engineering

1. Validate the metric alert rule 'test-alert': target metric, threshold, operator, evaluation frequency, and dimensions.
2. Review App Service diagnostics and application logs (App Service Logs / Application Insights) for errors around the alert time.
3. Confirm deployment history and configuration changes near 2025-11-13T06:46:48Z and 2025-11-30 recent spikes.
4. Check health check endpoint configuration and availability, if enabled.
5. If the alert is intended as a test, update severity/routing to avoid Sev1 noise; otherwise tune thresholds.

References

• Azure Monitor Alert: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourcegroups/rg-sredemo/providers/microsoft.web/sites/sredemo-web/providers/Microsoft.AlertsManagement/alerts/c27e686c-52e0-4af8-a7d1-f24e7944f000

Please acknowledge ownership and provide ETA for triage. If additional telemetry (logs, traces, request IDs) is required, specify and we will attach.

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