[Incident 74b1991d-19c1-4bb2-99bf-600255dbf000] Azure Monitor 'test-alert' fired on sredemo-web

[TimoSalomaki]

Incident overview

• Incident ID: 74b1991d-19c1-4bb2-99bf-600255dbf000
• First Seen (UTC): 2025-11-21T23:53:35Z
• Detection Source: Azure Monitor (Metric Alert)
• Alert Rule: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourceGroups/rg-sredemo/providers/microsoft.insights/metricAlerts/test-alert
• Severity: Sev1
• Monitor Condition: Fired
• Impacted endpoints/users: Not specified (please update if known)

Environment

• Subscription ID: 7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf
• Resource Group: rg-sredemo
• Resource: App Service (Microsoft.Web/sites) – sredemo-web
• Resource ID: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourcegroups/rg-sredemo/providers/microsoft.web/sites/sredemo-web
• Region: Not specified
• Service tier/SKU: Not specified

Symptoms and errors

• Alert description was empty in the ticket. No explicit error messages or correlation IDs provided.
• Platform metrics indicate low traffic and no 5xx errors during the analyzed window.

Recent changes/activity (last 24h)

• No Azure Activity Logs were found for the resource or dependencies in the last 24 hours. This may indicate no recent administrative changes or logging gaps.

Metrics snapshot (past ~2 hours, UTC window ending at 2025-11-23T19:53Z)

• Requests: Very low volume (0–1 per minute), sporadic.
• Http5xx: 0 across the window – no server error responses observed.
• AverageResponseTime: Typical values around 7–18 ms when present; no latency spikes observed.
• MemoryWorkingSet: Stable ~190–196 MiB, gradual increase consistent with normal app behavior; no signs of exhaustion.
• InstanceCount: Not queried; available via metrics if needed.

Reproduction steps

• Not available. Please add steps if the alert correlates with specific endpoints or traffic patterns.

Attempted mitigations

• None applied. Investigation focused on validation, activity logs, and metrics baseline.

Proposed next steps for engineering

• Confirm alert rule configuration: thresholds, aggregation, and dimensions used by 'test-alert'. Ensure it targets the correct metric and resource.
• Verify App Service health checks and any custom probes; cross-check with HealthCheckStatus metric and App Service diagnostics.
• Review application logs (App Service Log Stream/Application Insights, if connected) around 2025-11-21T23:53Z for anomalies.
• Validate deployment history and config changes beyond 24h window if applicable.
• Confirm region and SKU, and whether any autoscale or infrastructure events occurred.

References

• Alert ID resource: /subscriptions/7ef48e25-fddf-4dc3-b10e-8b73bd7d5faf/resourcegroups/rg-sredemo/providers/microsoft.web/sites/sredemo-web/providers/Microsoft.AlertsManagement/alerts/74b1991d-19c1-4bb2-99bf-600255dbf000

Labels/Ownership

• Please acknowledge receipt and provide an ETA for triage. If this repo is not the correct ownership for sredemo-web, update with the correct repository or owner.

---

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