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

Azure Event Hubs SDK — JavaScript

Package: @azure/event-hubs | README | Full Troubleshooting Guide

Common Errors

| Error | Code | Fix | |-------|------|-----| | MessagingError (connection:forced) | Idle disconnect | Auto-recovers; no action needed | | MessagingError (Unauthorized) | Bad credentials | Verify connection string, SAS, or RBAC roles | | MessagingError (retryable: true) | Transient issue | Auto-retried per RetryOptions. If surfaced, all retries exhausted |

MessagingError fields: name, code, retryable, info, address, errno, port, syscall.

Enable Logging

# All SDK logs
export AZURE_LOG_LEVEL=verbose

# Or use DEBUG for granular control
export DEBUG=azure*,rhea*

# Errors only
export DEBUG=azure:*:(error|warning),rhea-promise:error,rhea:events,rhea:frames,rhea:io,rhea:flow

Browser:

localStorage.debug = "azure:*:info";

Key Issues

  • Socket exhaustion: Treat clients as singletons. Each new client creates a new AMQP connection/socket. Always call close().
  • 412 precondition failures: Normal during subscription partition ownership negotiation.
  • Partition ownership churn: Expected when scaling instances. Should stabilize within minutes.
  • High CPU: Limit to 1.5–3 partitions per CPU core.
  • Subscription stops receiving: Often a symptom of an underlying race condition during error recovery. File a GitHub issue with DEBUG logs.
  • WebSockets: Pass webSocketOptions to client constructor to connect over port 443.

Checkpointing (BlobCheckpointStore)

Package: @azure/eventhubs-checkpointstore-blob

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

const { BlobCheckpointStore } = require("@azure/eventhubs-checkpointstore-blob");
const { BlobServiceClient } = require("@azure/storage-blob");

const containerClient = new BlobServiceClient(storageEndpoint, credential)
  .getContainerClient("checkpointstore");
const checkpointStore = new BlobCheckpointStore(containerClient);

const consumerClient = new EventHubConsumerClient(
  consumerGroup, fullyQualifiedNamespace, eventHubName, credential, checkpointStore
);

Common issues:

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