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
For more information on supported dimensions, refer to [Azure documentation](https://learn.microsoft.com/en-us/azure/event-grid/monitor-push-reference#metrics).
27
24
@@ -30,123 +27,23 @@ For more information on supported dimensions, refer to [Azure documentation](htt
30
27
Azure service sends monitoring data to Azure Monitor, which can then [stream data to Eventhub](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/stream-monitoring-data-event-hubs). Sumo Logic supports:
31
28
32
29
* Logs collection from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) using our [Azure Event Hubs source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
33
-
* Metrics collection using our [HTTP Logs and Metrics source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/) via Azure Functions deployed using the ARM template.
30
+
* Metrics collection using our [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source).
34
31
35
32
You must explicitly enable diagnostic settings for each domain, namespace, custom topic, and system topic you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described [here](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#destination-limitations).
36
33
37
34
When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/EventGrid/Logs`, `Azure/EventGrid/Metrics`.
38
35
39
-
### Configure field in field schema
40
-
41
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**.
42
-
1. Search for the following fields:
43
-
-`tenant_name`. This field is tagged at the collector level. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name).
44
-
-`location`. The region to which the resource name belongs.
45
-
-`subscription_id`. ID associated with a subscription where the resource is present.
46
-
-`resource_group`. The resource group name where the Azure resource is present.
47
-
-`provider_name`. Azure resource provider name (for example, Microsoft.Network).
48
-
-`resource_type`. Azure resource type (for example, storage accounts).
49
-
-`resource_name`. The name of the resource (for example, storage account name).
50
-
-`service_type`. Type of the service that can be accessed with an Azure resource.
51
-
-`service_name`. Services that can be accessed with an Azure resource (for example, in Azure Event Grid service is Subscriptions).
52
-
1. Create the fields if they are not present. Refer to [Manage fields](/docs/manage/fields/#manage-fields).
53
-
54
-
### Configure field extraction rules
55
-
56
-
Create the following Field Extraction Rule(s) (FER) for Azure Storage by following the instructions in [Create a Field Extraction Rule](/docs/manage/field-extractions/create-field-extraction-rule/).
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, onto an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
38
+
To set up the Azure Metrics source in Sumo Logic, refer to [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source).
39
+
40
+
:::note
41
+
Sumo Logic Metrics source is currently in Beta, to participate, contact your Sumo Logic account executive.
42
+
:::
43
+
44
+
1. To set up the Azure Metrics source in Sumo Logic, refer to the shared beta documentation.
45
+
1. In the Sumo Logic Azure Metrics source configuration, configure namespaces as `Microsoft.EventGrid/domains`, `Microsoft.EventGrid/systemTopics` and `Microsoft.EventGrid/topics`.
141
46
142
-
1. Create a hosted collector and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
143
-
1.[Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
144
-
1.[Configure and deploy the ARM Template](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-2-configure-azure-resources-using-arm-template).
145
-
1.[Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform the steps below for each Azure Event Grid namespace that you want to monitor.
146
-
1. Choose `Stream to an event hub` as the destination.
147
-
1. Select `AllMetrics`.
148
-
1. Use the Event Hub namespace created by the ARM template in Step 2 above. You can create a new Event Hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/send-data/azure-event-grid-metrics.png')} alt="Azure event grid metrics" style={{border: '1px solid gray'}} width="800" />
149
-
1. Tag the location field in the source with the right location value. <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Event Grid Tag Location" style={{border: '1px solid gray'}} width="400" />
150
47
151
48
### Configure logs collection
152
49
@@ -172,19 +69,31 @@ Since this source contains logs from multiple regions, make sure that you do not
172
69
173
70
Now that you have set up data collection, install the Azure Event Grid Sumo Logic app to use the pre-configured [dashboards](#viewing-the-azure-event-grid-dashboards) that provide visibility into your environment for real-time analysis of Azure resources.
174
71
175
-
import AppInstallNoDataSourceV2 from '../../reuse/apps/app-install-index-apps-v2.md';
72
+
import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md';
176
73
177
-
<AppInstallNoDataSourceV2/>
74
+
<AppInstallIndexV2/>
75
+
76
+
As part of the app installation process, the following fields will be created by default:
77
+
78
+
-`tenant_name`. This field is tagged at the collector level. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name).
79
+
-`location`. The region the resource name belongs to.
80
+
-`subscription_id`. ID associated with a subscription where the resource is present.
81
+
-`resource_group`. The resource group name where the Azure resource is present.
82
+
-`provider_name`. Azure resource provider name (for example, Microsoft.Network).
83
+
-`resource_type`. Azure resource type (for example, storage accounts).
84
+
-`resource_name`. The name of the resource (for example, storage account name).
85
+
-`service_type`. Type of the service that can be accessed with an Azure resource.
86
+
-`service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions).
178
87
179
88
## Viewing the Azure Event Grid dashboards
180
89
181
-
import ViewDashboards from '../../reuse/apps/view-dashboards.md';
90
+
import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md';
182
91
183
-
<ViewDashboards/>
92
+
<ViewDashboardsIndex/>
184
93
185
94
### Overview
186
95
187
-
**Azure Event Grid - Overview** dashboard provides details on the performance, authentication, and delivery status of your Azure Event Grid service.
96
+
The **Azure Event Grid - Overview** dashboard provides details on the performance, authentication, and delivery status of your Azure Event Grid service.
188
97
189
98
Use this dashboard to:
190
99
* Monitor request patterns by location and network access type to optimize resource allocation and improve latency.
@@ -196,7 +105,7 @@ Use this dashboard to:
196
105
197
106
### Administrative Operations
198
107
199
-
**Azure Event Grid - Administrative Operations** dashboard provides details on the operational activities and status of your Azure Event Grid resources.
108
+
The **Azure Event Grid - Administrative Operations** dashboard provides details on the operational activities and status of your Azure Event Grid resources.
200
109
201
110
Use this dashboard to:
202
111
* Monitor the distribution of operation types and their success rates to ensure the proper functioning of your Event Grid system.
**Azure Event Grid - Errors** dashboard provides details on various error types, failed deliveries, and dropped events in your Azure Event Grid service.
119
+
The **Azure Event Grid - Topic Errors** dashboard provides details on various error types, failed deliveries, and dropped events in your Azure Event Grid service for system topics and topics.
211
120
212
121
Use this dashboard to:
213
122
* Identify the most common error types affecting event publishing and delivery, such as "NotFound" and "Cancelled" errors.
214
123
* Analyze trends in delivery attempt failures and correlate them with specific resource groups or topics to pinpoint problematic areas.
215
124
* Monitor dropped event counts over time and investigate the reasons behind event drops to improve system reliability.
216
125
* Track the top failed topics and delivery destinations to prioritize troubleshooting efforts and optimize event routing.
The **Azure Event Grid - Domain Errors** dashboard provides details on various error types, failed deliveries, and dropped events in your Azure Event Grid service for domains. You can filter the dashboard results for particular topic using the topic filter
132
+
133
+
Use this dashboard to:
134
+
* Identify the most common error types affecting event publishing and delivery, such as "NotFound" and "Cancelled" errors.
135
+
* Analyze trends in delivery attempt failures and correlate them with specific resource groups or topics to pinpoint problematic areas.
136
+
* Monitor dropped event counts over time and investigate the reasons behind event drops to improve system reliability.
137
+
* Track the top failed topics and delivery destinations to prioritize troubleshooting efforts and optimize event routing.
The **Azure Event Grid - Topic Operations** dashboard provides details on the performance and reliability of your Event Grid service, including processing times, success rates, and failure percentages for system topics and topics.
144
+
145
+
Use this dashboard to:
146
+
* Monitor the average destination processing duration to identify potential bottlenecks or performance issues in event delivery.
147
+
* Track delivery failure percentages over time to quickly spot and address any spikes in unsuccessful event transmissions.
148
+
* Analyze the correlation between unmatched event percentages and advanced filter evaluation counts to optimize event routing and filtering.
149
+
* Identify trends in publish success latency and failure rates to ensure efficient event publishing and processing.
**Azure Event Grid - Operations** dashboard provides details on the performance and reliability of your Event Grid service, including processing times, success rates, and failure percentages.
155
+
The **Azure Event Grid - Domain Operations** dashboard provides details on the performance and reliability of your Event Grid service, including processing times, success rates, and failure percentages for domains. You can filter the dashboard results for particular topic using the topic filter.
223
156
224
157
Use this dashboard to:
225
158
* Monitor the average destination processing duration to identify potential bottlenecks or performance issues in event delivery.
226
159
* Track delivery failure percentages over time to quickly spot and address any spikes in unsuccessful event transmissions.
227
160
* Analyze the correlation between unmatched event percentages and advanced filter evaluation counts to optimize event routing and filtering.
228
161
* Identify trends in publish success latency and failure rates to ensure efficient event publishing and processing.
**Azure Event Grid - Policy and Recommendations** dashboard provides details on policy events and recommendations for your Azure Event Grid resources.
167
+
The **Azure Event Grid - Policy and Recommendations** dashboard provides details on policy events and recommendations for your Azure Event Grid resources.
235
168
236
169
Use this dashboard to:
237
170
* Monitor the success and failure rates of policy events to ensure proper configuration and compliance.
0 commit comments