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

Azure Service Bus SDK — JavaScript

Package: @azure/service-bus | README | Full Troubleshooting Guide

Common Errors

| Error Code | Cause | Fix | |------------|-------|-----| | ServiceTimeout | Service didn't respond; or no unlocked sessions | Transient — auto-retried. Verify state if persists | | MessageLockLost | Processing exceeded lock duration or link detached | Reduce processing time, ensure autolock renewal works | | SessionLockLost | Session lock expired or link detached | Re-accept session, keep renewing lock | | QuotaExceeded | Too many concurrent receives | Reduce receivers or use batch receives | | MessageSizeExceeded | Message or batch > max size | Reduce payload. Premium supports individual messages up to 100MB. Batch limit is computed from max message size on the client, so batches can also be impacted | | UnauthorizedAccess | Bad credentials | Verify connection string, SAS, or RBAC roles |

ServiceBusError fields: code, retryable, name, info, address.

Enable Logging

# All SDK logs
export AZURE_LOG_LEVEL=verbose

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

# Errors only
export DEBUG=azure:service-bus:error,azure:core-amqp:error,rhea-promise:error,rhea:events,rhea:frames,rhea:io,rhea:flow

Log to file:

node app.js > out.log 2>debug.log

Key Issues

  • Socket exhaustion: Treat ServiceBusClient as singleton. Each creates a new AMQP connection. Always call close().
  • Lock lost before expiry: Can happen on link detach (transient network issue or 10-min idle timeout). Not always due to processing time.
  • Batch receive returns fewer messages: After first message arrives, receiver waits only 1s for additional messages. maxWaitTimeInMs controls wait for the first message only.
  • Autolock renewal not working: Ensure system clock is accurate. Autolock relies on system time.
  • 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.
  • WebSockets: Pass webSocketOptions to ServiceBusClient constructor for port 443 connectivity.
  • Distributed tracing: Experimental OpenTelemetry support via @azure/opentelemetry-instrumentation-azure-sdk.