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-eventhubs-dotnet.md

Azure Event Hubs SDK — .NET (C#)

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

Common Errors

| Exception | Reason | Fix | |-----------|--------|-----| | EventHubsException (ServiceTimeout) | Service didn't respond in time | Transient — retried automatically. Verify state if persists | | EventHubsException (QuotaExceeded) | Too many active readers per consumer group | Reduce concurrent receivers or upgrade tier | | EventHubsException (ConsumerDisconnected) | Higher priority consumer took ownership | Expected during load balancing; check if scaling | | EventHubsException (MessageSizeExceeded) | Event too large | Reduce event payload; unlikely in practice since the client caps at the service link limit | | UnauthorizedAccessException | Bad credentials | Verify connection string, SAS token, or RBAC roles |

Exception Filtering

try { /* receive events */ }
catch (EventHubsException ex) when (ex.Reason == EventHubsException.FailureReason.ConsumerDisconnected)
{
    // Handle consumer disconnection
}

Retry Configuration

Configure via EventHubsRetryOptions when creating the client. See Configuring retry thresholds sample.

Key Issues

  • Socket exhaustion: Treat clients as singletons. Share EventHubConnection across clients if needed. Always call CloseAsync or DisposeAsync.
  • HTTP 412/409 from storage: Normal during checkpoint store operations — not an error.
  • Partitions closing frequently: Expected when scaling. If persists >5 min without scaling, investigate. See Troubleshooting Guide for detailed diagnostics.
  • High CPU: Limit to 1.5–3 partitions per CPU core and test at scale thoroughly if above that threshold.
  • Azure Functions: After upgrading to v5.0+ extensions, update binding types. Reduce logging noise by filtering Azure.Messaging.EventHubs to Warning.
  • WebSockets: Use EventHubsTransportType.AmqpWebSockets to connect over port 443 when AMQP ports (5761, 5762) are blocked.

Checkpointing (BlobCheckpointStore)

Package: Azure.Messaging.EventHubs.Processor (includes EventProcessorClient + blob checkpoint store)

Auth: DefaultAzureCredential is for local development. See auth-best-practices.md for production patterns.

var credential = new DefaultAzureCredential();

var storageClient = new BlobContainerClient(
    new Uri("https://<storage-account>.blob.core.windows.net/<checkpoint-container>"),
    credential);

var processor = new EventProcessorClient(
    storageClient,
    "$Default",
    "<your-namespace>.servicebus.windows.net",
    "<your-eventhub>",
    credential);

processor.ProcessEventAsync += async (args) =>
{
    // process event
    await args.UpdateCheckpointAsync();
};

Common issues:

  • Soft delete / blob versioning: Disable both on the storage account — they cause delays during load balancing.
  • HTTP 412/409 from storage: Normal during partition ownership negotiation; not an error.
  • Checkpoint frequency: Call UpdateCheckpointAsync() per batch, not per event, to reduce storage calls.