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: packages/azure_app_service/_dev/build/docs/README.md
+5-36Lines changed: 5 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,44 +16,13 @@ This integration currently collects one data stream:
16
16
17
17
- App Service Logs
18
18
19
-
## Requirements
20
-
21
-
### Credentials
22
-
23
-
`eventhub` :
24
-
_string_
25
-
Is the fully managed, real-time data ingestion service.
26
-
27
-
`consumer_group` :
28
-
_string_
29
-
The publish/subscribe mechanism of Event Hubs is enabled through consumer groups. A consumer group is a view (state, position, or offset) of an entire event hub. Consumer groups enable multiple consuming applications to each have a separate view of the event stream, and to read the stream independently at their own pace and with their own offsets.
30
-
Default value: `$Default`
31
-
32
-
`connection_string` :
33
-
_string_
34
-
The connection string required to communicate with Event Hubs, steps here https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string.
35
-
36
-
A Blob Storage account is required in order to store/retrieve/update the offset or state of the eventhub messages. This means that after stopping the filebeat azure module it can start back up at the spot that it stopped processing messages.
37
-
38
-
`storage_account` :
39
-
_string_
40
-
The name of the storage account the state/offsets will be stored and updated.
41
-
42
-
`storage_account_key` :
43
-
_string_
44
-
The storage account key, this key will be used to authorize access to data in your storage account.
45
-
46
-
`resource_manager_endpoint` :
47
-
_string_
48
-
Optional, by default we are using the azure public environment, to override, users can provide a specific resource manager endpoint in order to use a different azure environment.
49
-
Ex:
50
-
https://management.chinacloudapi.cn/ for azure ChinaCloud
51
-
https://management.microsoftazure.de/ for azure GermanCloud
52
-
https://management.azure.com/ for azure PublicCloud
53
-
https://management.usgovcloudapi.net/ for azure USGovernmentCloud
54
-
Users can also use this in case of a Hybrid Cloud model, where one may define their own endpoints.
19
+
## Requirements and setup
20
+
Refer to the [Azure Logs](https://docs.elastic.co/integrations/azure) page for more information on how to set up and use this integration.
55
21
56
22
## App Service Logs
23
+
Collects different types of logs from Azure App Service via Event Hub.
Copy file name to clipboardExpand all lines: packages/azure_app_service/docs/README.md
+57-36Lines changed: 57 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,44 +16,65 @@ This integration currently collects one data stream:
16
16
17
17
- App Service Logs
18
18
19
-
## Requirements
20
-
21
-
### Credentials
22
-
23
-
`eventhub` :
24
-
_string_
25
-
Is the fully managed, real-time data ingestion service.
26
-
27
-
`consumer_group` :
28
-
_string_
29
-
The publish/subscribe mechanism of Event Hubs is enabled through consumer groups. A consumer group is a view (state, position, or offset) of an entire event hub. Consumer groups enable multiple consuming applications to each have a separate view of the event stream, and to read the stream independently at their own pace and with their own offsets.
30
-
Default value: `$Default`
31
-
32
-
`connection_string` :
33
-
_string_
34
-
The connection string required to communicate with Event Hubs, steps here https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string.
35
-
36
-
A Blob Storage account is required in order to store/retrieve/update the offset or state of the eventhub messages. This means that after stopping the filebeat azure module it can start back up at the spot that it stopped processing messages.
37
-
38
-
`storage_account` :
39
-
_string_
40
-
The name of the storage account the state/offsets will be stored and updated.
41
-
42
-
`storage_account_key` :
43
-
_string_
44
-
The storage account key, this key will be used to authorize access to data in your storage account.
45
-
46
-
`resource_manager_endpoint` :
47
-
_string_
48
-
Optional, by default we are using the azure public environment, to override, users can provide a specific resource manager endpoint in order to use a different azure environment.
49
-
Ex:
50
-
https://management.chinacloudapi.cn/ for azure ChinaCloud
51
-
https://management.microsoftazure.de/ for azure GermanCloud
52
-
https://management.azure.com/ for azure PublicCloud
53
-
https://management.usgovcloudapi.net/ for azure USGovernmentCloud
54
-
Users can also use this in case of a Hybrid Cloud model, where one may define their own endpoints.
19
+
## Requirements and setup
20
+
Refer to the [Azure Logs](https://docs.elastic.co/integrations/azure) page for more information on how to set up and use this integration.
55
21
56
22
## App Service Logs
23
+
Collects different types of logs from Azure App Service via Event Hub.
24
+
25
+
An example event for `app_service` looks as following:
0 commit comments