Azure Service Bus: diagnose message-lock loss before extending auto-renewal
A production runbook for separating processing time, connection loss, renewal failure and late settlement before extending an Azure Service Bus message lock.
Read article
Tag
incident
19 articles connected to this technical signal.
Azure Network Watcher: diagnose an intermittent path before changing NSG or UDR
A production runbook for turning intermittent Azure connectivity into continuous evidence with Connection Monitor, then isolating DNS, routing, filtering and service health before changing network policy.
Read articleAzure Monitor: contain log alert fan-out before changing the KQL rule
A production runbook for measuring split-by dimension cardinality, containing notification noise, canarying stable grouping and rolling back an Azure Monitor log alert without losing coverage.
Read articleAzure Logic Apps: diagnose duplicate runs before disabling retries
A production runbook for separating redelivery, splitOn, concurrency and ambiguous retries, then enforcing idempotency without removing workflow resilience.
Read articleAKS: diagnose intermittent DNS before restarting CoreDNS
A production runbook for separating pod resolver, CoreDNS, service path, upstream DNS and node-specific failures before restarting or rolling back AKS DNS.
Read articleAzure DevOps: contain a secret exposed in logs before rerunning the pipeline
A production runbook for bounding a secret leak in Azure DevOps logs, preserving evidence, revoking access, validating redaction and deciding recovery or rollback.
Read articleMicrosoft Entra PIM: diagnose Azure role activation before granting permanent access
A production runbook for separating PIM eligibility, activation, approval, Conditional Access, RBAC propagation and effective ARM access before any permanent bypass.
Read articleAzure Monitor: diagnose suppressed notifications before changing the alert
A production runbook to prove that an alert processing rule suppresses notifications, bound its scope, validate recovery, and keep a rollback path.
Read articleAzure Automation: diagnose a Hybrid Runbook Worker that stops picking up jobs
A production runbook for separating queueing, heartbeat, extension, network, capacity, identity and runtime failures before retrying a Hybrid Worker job.
Read articleAzure Service Health: qualify a regional signal before failover
A production runbook for qualifying an Azure Service Health or Resource Health signal with user impact, dependencies, routing, DNS, observability, failover decision and rollback.
Read articleAzure Monitor: diagnose an Action Group before silencing alerts
A production runbook for qualifying an Azure Monitor Action Group by separating rules, receivers, webhooks, escalation paths, KQL evidence, validation and rollback before reducing notifications.
Read articleAzure Cosmos DB: diagnose 429 throttling before increasing RU/s
A production runbook for qualifying Cosmos DB 429 throttling with RU consumption, hot partitions, query shape, SDK retries, indexing, KQL evidence, scaling decision and rollback.
Read articleAzure Monitor Action Groups: diagnose missing notifications before changing alerts
A production runbook for qualifying an Azure Monitor alert that fired but did not notify anyone, with action groups, receivers, processing rules, webhooks, evidence, validation and rollback.
Read articleAWX: rerun a failed job without replaying a partial action
A production runbook for qualifying a failed AWX job with Ansible events, changed tasks, affected hosts, variables, limited rerun, validation and rollback.
Read articleAWX snippet: capture failed job evidence before rerun
A short sequence to collect status, variables, affected host and error events before rerunning an AWX job.
Read articleAgentOps: diagnose an AI agent action before rollback
A production runbook for qualifying an AI agent action with traces, sources, tools, identity, KQL, human validation and rollback without disabling the whole assistant.
Read articleAzure Monitor and KQL: decide a deployment rollback without silencing alerts
A production runbook for deciding an Azure rollback after deployment with Azure Monitor, KQL, impact correlation, regression evidence, validation and controlled recovery.
Read articleAzure Monitor: diagnose an alert storm after deployment
A production runbook for qualifying an Azure Monitor alert storm after deployment by separating real signal, noise, regression, threshold drift, action group behavior and rollback.
Read articleMonitoring: turn an alert into an actionable operations runbook
Build useful alerts by connecting signal, diagnosis, scope, decision and rollback path instead of accumulating noisy notifications.
Read article