Edit

Monitoring Azure Operator Insights

  • Article

When you have critical applications and business processes relying on Azure resources, you want to monitor those resources for their availability, performance, and operation.

Azure Operator Insights Data Products use Azure Monitor. They collect the same kinds of monitoring data as other Azure resources that are described in Monitoring data from Azure resources. See Monitoring Azure Operator Insights data reference for detailed information on the monitoring data created by Data Products.

Tip

If you're unfamiliar with the features of Azure Monitor common to all Azure services that use it, read Monitoring Azure resources with Azure Monitor.

Ingestion agents also collect monitoring data that you or Microsoft Support can use for troubleshooting.

Metrics for Data Products: Overview, collection and analysis

Azure Operator Insights doesn't provide metrics in Azure Monitor.

Activity logs for Data Products: Overview, collection and analysis

The Activity log is a type of platform log in Azure that provides insight into subscription-level events. For Azure Operator Insights, the Activity log includes activities like creating a Data Product or changing its settings.

The Activity log is collected and stored automatically by Azure. You can:

Resource logs for Data Products: Overview, collection and analysis

Resource logs provide an insight into operations that were performed within an Azure resource. This is known as the data plane. For Data Products, resource logs include ingestion (activity on files uploaded to Azure Operator Insights), digestion (processing the data in those files), and management of the processed data.

Resource logs aren't collected and stored until you create a diagnostic setting that routes them to one or more locations. We recommend routing them to a Log Analytics workspace, which stores the logs in Azure Monitor Logs. Log Analytics allows you to analyze the logs of all your Azure resources together in Azure Monitor Logs and take advantage of all the features available to Azure Monitor Logs including log queries and log alerts.

For instructions on using getting started with Log Analytics and creating a diagnostic setting, see Get started with resource logs for Data Products. For more information about the data available, see Data Product information in Azure Monitor Logs.

Get started with resource logs for Data Products

To start monitoring a Data Product with Azure Monitor Logs and Log Analytics:

  1. Create a Log Analytics workspace by following Create a Log Analytics workspace.
  2. In the Diagnostic setting view of your Data Product, create a diagnostic setting that routes the logs that you want to collect to the Log Analytics workspace. To use the example query in this procedure, include Database Query (in addition to any other category of logs that you want to collect).
  3. To use the example query in this procedure, run a query on the data in your Data Product by following Query data in the Data Product. This step ensures that Azure Monitor Logs has some data for your Data Product.
  4. Return to your Data Product resource and select Logs from the Azure Operator Insights menu to access Log Analytics.
  5. Run the following query to view the log for the query that you ran on your Data Product, replacing username@example.com with the email address you used when you ran the query. You can also adapt the sample queries in Sample Kusto queries. 
    AOIDatabaseQuery
| where User has_cs "username@example.com"
| take 100

Important

When you select Logs from the Azure Operator Insights menu, Log Analytics is opened with the query scope set to the current Data Product. This means that log queries will only include data from that resource. If you want to run a query that includes data from other Data Products or data from other Azure services, select Logs from the Azure Monitor menu. See Log query scope and time range in Azure Monitor Log Analytics for details.

Data Product information in Azure Monitor Logs

For a full list of the types of resource logs collected for Azure Operator Insights, see Monitoring Azure Operator Insights data reference: Resource logs.

Data in Azure Monitor Logs is stored in tables where each table has its own set of unique properties. For a list of the Azure Operator Insights tables used by Azure Monitor Logs and queryable by Log Analytics, see Monitoring Azure Operator Insights data reference: Azure Monitor Logs tables.

All resource logs in Azure Monitor have the same fields followed by service-specific fields. The common schema is outlined in Azure Monitor resource log schema The schemas for Azure Operator Insights resource logs are found in the Azure Operator Insights Data Reference: Schemas.

Sample Kusto queries

You can use the following example queries in a Log Analytics workspace to help you monitor your Data Products:

  • Get all logs about rows that weren't digested successfully:

    AOIDigestion
| where Message startswith_cs "Failed to decode row"
| take 100

  • Get a breakdown of the number of files that weren't digested, grouped by the top-level directory that they were uploaded to (typically the SiteId):

    AOIDigestion
| where Message startswith_cs "Failed to digest file"
| parse FilePath with Source:string "/" *
| summarize count() by Source

  • List all the queries run on a Quality of Experience - MCC Data Product by a particular user:

    AOIDatabaseQuery
| where DatabaseName has_cs "edrdp" and User has_cs "username@example.com"
| take 100

  • List all the ingestion operations performed on input storage of a Data Product:

    AOIStorage
| where Category has_cs "Ingestion"
| take 100

  • List all delete operations performed on input storage of a Data Product:

    AOIStorage
| where Category has_cs "IngestionDelete"
| take 100

  • List all Read operations performed on storage of a Data Product:

    AOIStorage
| where Category has_cs "ReadStorage"
| take 100

For a list of common queries for Azure Operator Insights, see the Log Analytics queries interface.

Monitoring for ingestion agents

Azure Operator Insights also requires ingestion agents deployed in your network.

Ingestion agents that we provide automatically collect metrics and logs for troubleshooting. Metrics and logs are stored on the VM on which you installed the agent, and aren't uploaded to Azure Monitor. For details, see Monitor and troubleshoot ingestion agents for Azure Operator Insights.

Next steps