AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-diagnostics

Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-diagnostics at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 42

troubleshooting/messaging/azure-servicebus-dotnet.md

Azure Service Bus SDK — .NET (C#)

Package: Azure.Messaging.ServiceBus | README | Full Troubleshooting Guide

Common Errors

| Exception | Reason | Fix | |-----------|--------|-----| | ServiceBusException (ServiceTimeout) | Service didn't respond | Transient — auto-retried. For session accept, means no unlocked sessions | | ServiceBusException (MessageLockLost) | Lock expired or link detached | Renew lock, reduce processing time, check network | | ServiceBusException (SessionLockLost) | Session lock expired | Re-accept session, renew lock before expiry | | ServiceBusException (QuotaExceeded) | Too many concurrent receives | Reduce receivers or use batch receives | | ServiceBusException (MessageSizeExceeded) | Message or batch too large | Reduce payload. Premium tier supports individual messages up to 100MB. Batch limit is artificially computed on the client from the max message size sent by the service, so batches can also be impacted | | ServiceBusException (ServiceBusy) | Request throttled | Auto-retried with 10s backoff. See throttling docs | | UnauthorizedAccessException | Bad credentials | Verify connection string, SAS, or RBAC roles |

Exception Filtering

try { /* receive messages */ }
catch (ServiceBusException ex) when (ex.Reason == ServiceBusFailureReason.ServiceTimeout)
{
    // Handle timeout
}

Key Issues

  • Socket exhaustion: Treat ServiceBusClient as singleton. Each creates a new AMQP connection. Always call CloseAsync/DisposeAsync.
  • Lock lost before expiry: Can happen on link detach (transient network) or 10-min idle timeout.
  • Processor high concurrency: May cause hangs with extreme concurrency settings. Test with moderate values.
  • Session processor slow switching: Tune SessionIdleTimeout to reduce wait time between sessions.
  • Batch size limits: Batch limit is artificially computed on the client from the max message size sent by the service. Send large messages individually if batch creation fails.
  • Transactions across entities: Requires all entities on same namespace. Use ServiceBusClient.CreateSender with via entity support.
  • WebSockets: Use ServiceBusTransportType.AmqpWebSockets when AMQP ports (5761, 5762) are blocked.