Skip to content

Commit 1ce5e7d

Browse files
committed
Troubleshoot connectivity articles
1 parent 9024a56 commit 1ce5e7d

File tree

2 files changed

+20
-7
lines changed

2 files changed

+20
-7
lines changed

articles/event-hubs/includes/event-hubs-connectivity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: include file
3-
description: include file
2+
title: Troubleshoot connectivity issues
3+
description: Include file with some common content that helps you with troubleshooting connectivity issues.
44
author: spelluru
55
ms.service: event-hubs
66
ms.topic: include
7-
ms.date: 12/15/2022
7+
ms.date: 07/29/2024
88
ms.author: spelluru
99
ms.custom: "include file"
1010

@@ -48,7 +48,7 @@ Also, verify that the IP address for your namespace is allowed. To find the righ
4848
```
4949
2. Note down the IP address returned in `Non-authoritative answer`.
5050
51-
If you use a namespace hosted in an older cluster (based on Cloud Services - CNAME ending in *.cloudapp.net) and the namespace is **zone redundant**, you will need to follow few extra steps below. If your namespace is on a newer cluster (based on Virtual Machine Scale Set (VMSS) - CNAME ending in *.cloudapp.azure.com) and zone redundant you can skip below steps.
51+
If you use a namespace hosted in an older cluster (based on Cloud Services - CNAME ending in *.cloudapp.net) and the namespace is **zone redundant**, you'll need to follow few extra steps below. If your namespace is on a newer cluster (based on Virtual Machine Scale Set (VMSS) - CNAME ending in *.cloudapp.azure.com) and zone redundant you can skip below steps.
5252
5353
1. First, you run nslookup on the namespace.
5454

articles/event-hubs/troubleshooting-guide.md

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,24 @@
22
title: Troubleshoot connectivity issues - Azure Event Hubs | Microsoft Docs
33
description: This article provides information on troubleshooting connectivity issues with Azure Event Hubs.
44
ms.topic: article
5-
ms.date: 12/15/2022
5+
ms.date: 07/29/2024
66
---
77

88
# Troubleshoot connectivity issues - Azure Event Hubs
9-
There are various reasons for client applications not able to connect to an event hub. The connectivity issues might be permanent or transient. If the issue happens all the time (permanent), you might want to check the connection string, your organization's firewall settings, IP firewall settings, network security settings (service endpoints, private endpoints, etc.), and more. For transient issues, upgrading to latest version of the SDK, running commands to check dropped packets, and obtaining network traces might help with troubleshooting the issues. This article provides tips for troubleshooting connectivity issues with Azure Event Hubs.
9+
There are various reasons for client applications not able to connect to an event hub. The connectivity issues might be permanent or transient.
10+
11+
If the issue happens all the time (**permanent**), check these settings and other options mentioned in the [Troubleshoot permanent connectivity issues](#troubleshoot-permanent-connectivity-issues) section in this article.
12+
13+
- Connection string
14+
- Your organization's firewall settings
15+
- IP firewall settings
16+
- Network security settings (service endpoints, private endpoints, etc.), and more
17+
18+
For **transient issues**, try the following options that can help with troubleshooting the issues. For more information, see [Troubleshoot transient connectivity issues](#troubleshoot-transient-connectivity-issues).
19+
20+
- Upgrade to latest version of the SDK
21+
- Run commands to check dropped packets
22+
- Obtain network traces.
1023

1124
## Troubleshoot permanent connectivity issues
1225
If the application isn't able to connect to the event hub at all, follow steps from this section to troubleshoot the issue.
@@ -22,7 +35,7 @@ For Kafka clients, verify that producer.config or consumer.config files are conf
2235
[!INCLUDE [event-hubs-connectivity](./includes/event-hubs-connectivity.md)]
2336

2437
### Verify that Event Hubs service tag is allowed in your network security groups
25-
If your application is running inside a subnet and there's an associated network security group, confirm whether the internet outbound is allowed or Event Hubs service tag (`EventHub`) is allowed. See [Virtual network service tags](../virtual-network/service-tags-overview.md) and search for `EventHub`.
38+
If your application is running inside a subnet and there's an associated network security group, confirm whether the internet outbound traffic is allowed or Event Hubs service tag (`EventHub`) is allowed. See [Virtual network service tags](../virtual-network/service-tags-overview.md) and search for `EventHub`.
2639

2740
### Check if the application needs to be running in a specific subnet of a virtual network
2841
Confirm that your application is running in a virtual network subnet that has access to the namespace. If it's not, run the application in the subnet that has access to the namespace or add the IP address of the machine on which application is running to the [IP firewall](event-hubs-ip-filtering.md).

0 commit comments

Comments
 (0)