You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/filebeat/filebeat-input-azure-eventhub.md
+52-12Lines changed: 52 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,38 +12,78 @@ Users can make use of the `azure-eventhub` input in order to read messages from
12
12
13
13
Users can enable internal logs tracing for this input by setting the environment variable `BEATS_AZURE_EVENTHUB_INPUT_TRACING_ENABLED: true`. When enabled, this input will log additional information to the logs. Additional information includes partition ownership, blob lease information, and other internal state.
14
14
15
-
Example configuration using Shared Access Key authentication:
# For Azure Government, use: "https://login.microsoftonline.us"
76
+
# For Azure China, use: "https://login.chinacloudapi.cn"
77
+
# Storage account configuration
78
+
storage_account: "your-storage-account"
79
+
storage_account_container: ""# Optional: defaults to filebeat-<eventhub-name>
44
80
processor_version: "v2"
81
+
# Optional: for non-public Azure clouds
82
+
# resource_manager_endpoint: "https://management.usgovcloudapi.net/" # For Azure Government
45
83
```
46
84
85
+
**Note:** When using `client_secret` authentication, the service principal must have the appropriate Azure RBAC permissions. See [Required permissions](#_required_permissions) for details.
86
+
47
87
## Authentication [_authentication]
48
88
49
89
The azure-eventhub input supports multiple authentication methods. The [`auth_type` configuration option](#_auth_type) controls the authentication method used for both Event Hub and Storage Account.
0 commit comments