Skip to content

[Incident] Sev1 - High 5xx Error Rate Alert on db-timetable-mcp-server (2026-06-08T21:48Z) #18

Description

@abeckDev

Incident Summary

Alert Rule: DB Timetable MCP Server Health Check
Severity: Sev1
Fired At: 2026-06-08T21:48:42 UTC
Resource: db-timetable-mcp-server (Container App, Sweden Central)
Resource ID: /subscriptions/b814d650-0963-4701-9dc9-feffc970ad6a/resourceGroups/db-timetable-mcp/providers/Microsoft.App/containerApps/db-timetable-mcp-server

Alert Condition

  • Metric: Requests (5xx status code category)
  • Threshold: Count > 100 in 5-minute window
  • Observed Value: 250

Alert Description

Test alert: The DB Timetable MCP Server container app is experiencing high error rates. This is a test webhook trigger.

Investigation (Automated by SRE Agent)

Current App Status

Property Value
Provisioning State Succeeded
Running Status Running
Latest Revision db-timetable-mcp-server--0000006
Image ghcr.io/abeckdev/db-timetableapi-mcpserver:main-f9d4687
CPU (0.5 vCPU) 0% (last 30 min)
Memory (1Gi) 2% (last 30 min)
Request Count 0 (last 30 min)
Recent Deployments None

Preliminary Findings

  • The container app is running and healthy with no active traffic or errors in the past 30 minutes.
  • The alert payload explicitly identifies this as a test webhook trigger.
  • No recent deployments or configuration changes detected.
  • No 5xx errors observed in current metrics.

Next Steps

  • Confirm whether this was an intentional test alert.
  • If genuine, investigate whether the 5xx errors occurred before the 30-minute metrics window.
  • Review Log Analytics workspace for historical error patterns.

Automated incident created by Azure SRE Agent

This issue was created by sre-agent--205413df
Tracked by the SRE agent here

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions