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
@@ -23,33 +23,152 @@ For more information on supported metrics and dimensions, refer to the [Azure do
23
23
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:
24
24
25
25
* 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/).
26
-
* 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.
26
+
* Metrics collection using our [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source).
27
27
28
-
You must explicitly enable diagnostic settings for each machine-learning workspace 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).
28
+
You must explicitly enable diagnostic settings for each Machine Learning Workspace 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).
29
29
30
30
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/MachineLearning/Logs`, `Azure/MachineLearning/Metrics`.
31
31
32
+
### Configure collector
33
+
34
+
Create a hosted collector if not already configured 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). Make sure you create the required sources in this collector. <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" />
35
+
32
36
### Configure metrics collection
33
37
34
-
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
+
import MetricsSourceBeta from '../../reuse/metrics-source-beta.md';
35
39
36
-
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" />
37
-
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).
38
-
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).
39
-
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 machine learning workspace that you want to monitor.
40
-
* Choose `Stream to an event hub` as the destination.
41
-
* Select `AllMetrics`.
42
-
* 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 the ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
40
+
<MetricsSourceBeta/>
43
41
44
42
### Configure logs collection
45
43
46
44
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
47
-
45
+
#### Diagnostic logs
48
46
1. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
49
-
2. To create the Diagnostic settings in the Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings). Perform the steps below for each machine learning workspace that you want to monitor.
50
-
* Choose `Stream to an event hub` as the destination.
51
-
* Select `allLogs` or individual log categories.
52
-
* Use the Event hub namespace and Event hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
47
+
1. To create the diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#create-diagnostic-settings). Perform the steps below for each Azure Machine Learning namespace that you want to monitor.
48
+
1. Choose `Stream to an event hub` as the destination.
49
+
1. Select `allLogs`.
50
+
1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/send-data/azure-machinelearning-logs.png')} alt="Azure Machine Learning logs" style={{border: '1px solid gray'}} width="800" />
51
+
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 Machine Learning Tag Location" style={{border: '1px solid gray'}} width="400" />
52
+
53
+
#### Activity Logs
54
+
55
+
To collect activity logs, refer to the [Collecting Logs for the Azure Audit App from Event Hub](/docs/integrations/microsoft-azure/audit#collecting-logs-for-the-azure-audit-app-from-event-hub) section in the Azure Audit documentation. If you're already collecting activity logs for a subscription, you can skip this step.
56
+
:::note
57
+
Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag.
58
+
:::
59
+
60
+
## Installing the Azure Machine Learning app
61
+
62
+
import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md';
63
+
64
+
<AppInstallIndexV2/>
65
+
66
+
As part of the app installation process, the following fields will be created by default:
67
+
68
+
-`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).
69
+
-`location`. The region to which the resource name belongs to.
70
+
-`subscription_id`. ID associated with a subscription where the resource is present.
71
+
-`resource_group`. The resource group name where the Azure resource is present.
72
+
-`provider_name`. Azure resource provider name (for example, Microsoft.Network).
73
+
-`resource_type`. Azure resource type (for example, storage accounts).
74
+
-`resource_name`. The name of the resource (for example, storage account name).
75
+
-`service_type`. Type of the service that can be accessed with a Azure resource.
76
+
-`service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions).
77
+
78
+
## Viewing the Azure Machine Learning dashboards
79
+
80
+
import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md';
81
+
82
+
<ViewDashboardsIndex/>
83
+
84
+
### Overview
85
+
86
+
The **Azure Machine Learning - Overview** dashboard provides comprehensive details on events, operations and details such as overall number of errors, failures, model usage and quota utilization, operation types, ingress and egress of network data
The **Azure Machine Learning - Model** dashboard provides information on model details and model inference operations related to your Azure Machine Learning.
The **Azure Machine Learning - Compute** dashboard provides details on compute operations, events and usage such as CPU, GPU, Disk or memory to your Azure Machine Learning.
The **Azure Machine Learning - Data Events** dashboard provides details on all Data events such as DateSet, DataStore, DataLabel read/change events with results details and also environment data events related to your Azure Machine Learning.
The **Azure Machine Learning - Administrative Operations** dashboard provides details on the operational activities and status of your Azure Machine Learning resources.
111
+
112
+
Use this dashboard to:
113
+
* Monitor the distribution of operation types and their success rates to ensure proper functioning of your Machine Learning.
114
+
* Identify potential issues by analyzing the top operations causing errors and correlating them with specific users or applications.
115
+
* Track recent write and delete operations to maintain an audit trail of changes made to your Machine Learning.
The **Azure Machine Learning - Policy and Recommendations** dashboard provides details on policy events and recommendations for your Azure Machine Learning resources.
122
+
123
+
Use this dashboard to:
124
+
* Monitor the success and failure rates of policy events to ensure proper configuration and compliance.
125
+
* Track and analyse recent recommendations to improve the performance and security of your VM setup.
126
+
* Identify trends in policy events and recommendations over time to proactively address potential issues.
The **Azure Machine Learning - Jobs and Pipelines** dashboard provides details on operations, events and failures in jobs and pipelines of your Azure Machine Learning.
133
+
134
+
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.us-east-1.amazonaws.com/dashboards/AzureMachineLearning/Azure-Machine-Learning-Jobs-and-Pipelines.png')} alt="Azure Machine Learning - Jobs and Pipelines dashboard" style={{border: '1px solid gray'}} width="800" />
135
+
136
+
### Quota
137
+
138
+
The **Azure Machine Learning - Quota** dashboard provides details on quota related to your Azure Machine Learning such as Quota Utilization, Active Node, Active Cores, Idle Cores, etc.
The **Azure Machine Learning - Run** dashboard provides details on running experiments such as failed runs, errors in runs, completed or in-progress or started run
0 commit comments