azure-messaging

Solid

Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.

DevOps & Infrastructure 607 stars 93 forks Updated 2 months ago MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Azure Messaging SDK Troubleshooting ## Quick Reference | Property | Value | |----------|-------| | **Services** | Azure Event Hubs, Azure Service Bus | | **MCP Tools** | `mcp_azure_mcp_eventhubs`, `mcp_azure_mcp_servicebus` | | **Best For** | Diagnosing SDK connection, auth, and message processing issues | ## When to Use This Skill - SDK connection failures, auth errors, or AMQP link errors - Idle timeout, connection inactivity, or slow reconnection after disconnect - AMQP link detach or detach-forced errors - Message lock lost, message lock expired, lock renewal failures, or batch lock timeouts - Session lock lost, session lock expired, or session receiver errors - Event processor or message handler stops processing - Duplicate events or checkpoint offset resets - SDK configuration questions (retry, prefetch, batch size, receive batch behavior) ## MCP Tools | Tool | Command | Use | |------|---------|-----| | `mcp_azure_mcp_eventhubs` | Namespace/hub ops | List namespaces, hubs, consumer groups | | `mcp_azure_mcp_servicebus` | Queue/topic ops | List namespaces, queues, topics, subscriptions | | `mcp_azure_mcp_monitor` | `logs_query` | Query diagnostic logs with KQL | | `mcp_azure_mcp_resourcehealth` | `get` | Check service health status | | `mcp_azure_mcp_documentation` | Doc search | Search Microsoft Learn for troubleshooting docs | ## Diagnosis Workflow 1. **Identify the SDK and version** — Check the prompt for SDK and version clues; if not stated, proceed with di...

Details

Author
microsoft
Repository
microsoft/azure-skills
Created
3 months ago
Last Updated
2 months ago
Language
Bicep
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Solid

azure-messaging

Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.

1,998 Updated 2 months ago
microsoft
DevOps & Infrastructure Listed

azure-messaging

Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. USE FOR: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter DO NOT USE FOR: creating Event Hub or Service Bus resources (use azure-prepare), monitoring metrics (use azure-observability), cost analysis (use azure-cost-optimization)

353 Updated today
aiskillstore
DevOps & Infrastructure Solid

azure-event-hubs

Expert knowledge for Azure Event Hubs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Kafka clients/Streams, .NET SDK, Flink/Spark, geo-disaster recovery, or Premium processing units, and other Azure Event Hubs related development tasks. Not for Azure Service Bus (use azure-service-bus), Azure Event Grid (use azure-event-grid), Azure Notification Hubs (use azure-notification-hubs), Azure Stream Analytics (use azure-stream-analytics).

604 Updated 3 days ago
MicrosoftDocs