Skip to content

Commit 4e1d98e

Browse files
[DOCS] Outbound ports for Event Hub (#88)
Bump to v1.4.6
1 parent a6be13b commit 4e1d98e

File tree

3 files changed

+7
-1
lines changed

3 files changed

+7
-1
lines changed

CHANGELOG.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1+
## 1.4.6
2+
- [DOCS] Add outbound port requirements for Event Hub [#88](https://github.com/logstash-plugins/logstash-input-azure_event_hubs/pull/88)
3+
14
## 1.4.5
25
- Upgrade multiple dependencies such as `gson`, `log4j2`, `jackson` to make the plugin stable [#83](https://github.com/logstash-plugins/logstash-input-azure_event_hubs/pull/83)
36

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
1.4.5
1+
1.4.6

docs/index.asciidoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,9 @@ Many Azure services integrate with the Azure Event Hubs.
3131
https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-azure-monitor[Azure
3232
Monitor], for example, integrates with Azure Event Hubs to provide infrastructure metrics.
3333

34+
IMPORTANT: This plugin requires outbound connections to ports `tcp/443`, `tcp/9093`, `tcp/5671`, and `tcp/5672`,
35+
as noted in the https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-faq#what-ports-do-i-need-to-open-on-the-firewall[Microsoft Event Hub documentation].
36+
3437
===== Event Hub connection string
3538

3639
The plugin uses the connection string to access Azure Events Hubs. Find the

0 commit comments

Comments
 (0)