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-java.md

Azure Event Hubs SDK — Java

Package: azure-messaging-eventhubs | README | Full Troubleshooting Guide

⚠️ Note: The detailed Java troubleshooting guide has moved to Microsoft Learn.

Common Errors

| Exception | Cause | Fix | |-----------|-------|-----| | AmqpException (connection:forced) | Idle connection disconnected | Auto-recovers; no action needed | | AmqpException (unauthorized-access) | Bad credentials or missing permissions | Verify connection string, SAS, or RBAC roles | | AmqpException (resource-limit-exceeded) | Too many concurrent receivers | Reduce receiver count or upgrade tier | | OperationTimeoutException | Network issue or throttling | Check firewall, try AMQP over WebSockets (port 443) |

Enable Logging

Configure via SLF4J. Add logback-classic dependency and set level for com.azure.messaging.eventhubs:

<logger name="com.azure.messaging.eventhubs" level="DEBUG"/>

For AMQP frame tracing:

<logger name="com.azure.core.amqp" level="DEBUG"/>

See Java SDK logging docs for details.

Key Issues

  • High CPU / partition imbalance: Limit to 1.5–3 partitions per CPU core.
  • Consumer disconnected: Higher priority consumer took ownership. Expected during load balancing. Persistent issues without scaling indicate a problem.
  • Connection sharing: Reuse EventHubClientBuilder connections; avoid creating new clients per operation.

Checkpointing (BlobCheckpointStore)

Package: azure-messaging-eventhubs-checkpointstore-blob

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

TokenCredential credential = new DefaultAzureCredentialBuilder().build();

BlobContainerAsyncClient blobClient = new BlobContainerClientBuilder()
    .endpoint("https://<storage-account>.blob.core.windows.net/<checkpoint-container>")
    .credential(credential)
    .buildAsyncClient();

EventProcessorClient processor = new EventProcessorClientBuilder()
    .credential("<your-namespace>.servicebus.windows.net", "<your-eventhub>", credential)
    .consumerGroup("$Default")
    .checkpointStore(new BlobCheckpointStore(blobClient))
    .processEvent(eventContext -> {
        // process event
        eventContext.updateCheckpoint();
    })
    .buildEventProcessorClient();

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 updateCheckpoint() per batch, not per event, to reduce storage calls.

Filing Issues

Include: partition count, machine specs, instance count, max heap (-Xmx), average EventData size, traffic pattern, and DEBUG-level logs (±10 min from issue).