Monitoring Time Series Insights
When you have critical applications and business processes relying on Azure resources, you want to monitor those resources for their availability, performance, and operation. This article describes the monitoring data generated by Time Series Insights and how you can use the features of Azure Monitor to analyze and alert on this data.
The Overview page in the Azure portal for each Time Series Insights environment includes a brief view of the resource usage, such as the number of messages received and the number of bytes stored. This information is helpful, however only a small amount of the monitoring data is available from this pane. Some of this data is collected automatically and is available for analysis as soon as you create the resource. You can enable additional types of data collection with some configuration.
What is Azure Monitor
Time Series Insights creates monitoring data using Azure Monitor, which is a full stack monitoring service in Azure that provides a complete set of features to monitor your Azure resources in addition to resources in other clouds and on-premises.
Start with the article Monitoring Azure resources with Azure Monitor, which describes the following concepts:
- What is Azure Monitor?
- Costs associated with monitoring
- Monitoring data collected in Azure
- Configuring data collection
- Standard tools in Azure for analyzing and alerting on monitoring data
The following sections build on this article by describing the specific data gathered for Azure Time Series Insights. These sections also provide examples for configuring data collection and analyzing this data with Azure tools.
Monitoring data from Azure Time Series Insights
Azure Time Series Insights collects the same kinds of monitoring data as other Azure resources that are described in Monitoring data from Azure resources.
See Azure Time Series Insights monitoring data reference for a detailed reference of the logs and metrics that you can collect.
Collection and routing
Platform metrics are collected and stored automatically, but can be routed to other locations by using a diagnostic setting.
Resource Logs are not collected and stored until you create a diagnostic setting and route them to one or more locations. See Create diagnostic setting to collect platform logs and metrics in Azure for the detailed process for creating a diagnostic setting using the Azure portal, CLI, or PowerShell. When you create a diagnostic setting, you specify which categories of logs to collect.
You can collect logs from the following categories for Azure Time Series Insights:
|Ingress||The Ingress category tracks errors that occur in the ingress pipeline. This category includes errors that occur when receiving events (such as failures to connect to an Event Source) and processing events (such as errors when parsing an event payload).|
You can analyze metrics for Azure Time Series Insights, along with metrics from other Azure services, by opening Metrics from the Azure Monitor menu. See Getting started with Azure Metrics Explorer for details on using this tool.
For a list of the platform metrics collected, see Monitoring Azure Time Series Insights data reference
This example shows the count of bytes received from all event sources into your Azure Time Series Insights environment.
The example shows the count of bytes successfully processed and available for query in your Azure Time Series Insights environment.
You can access resource logs either as a blob in a storage account, as event data, or through Log Analytic queries.
Data in Azure Monitor Logs is stored in tables which each table having its own set of unique properties.
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. For a list of the types of resource logs collected for Azure Time Series Insights, see Azure Time Series Insights monitoring data reference.
Azure Time Series Insights stores data in the following tables.
|TSIIngress||The table that stores data from the Ingress category. The Ingress category tracks errors that occur in the ingress pipeline. This category includes errors that occur when receiving events (such as failures to connect to an Event Source) and processing events (such as errors when parsing an event payload).|
To route data to Azure Monitor Logs, you must create a diagnostic setting to send resource logs or platform metrics to a Log Analytics workspace. To learn more, see Collection and routing.
Following are queries that you can use to help you monitor your Azure Time Series Insights environment:
Get details on event source connection failures in the last five days:
TSIIngress | where OperationName == "Microsoft.TimeSeriesInsights/environments/eventsources/ingress/connect" | where _ResourceId contains "<your environment name, event source name, or the full event source resource URL>" | where TimeGenerated > ago(5d)
Get details on invalid messages received in the last five days:
TSIIngress | where OperationName == "Microsoft.TimeSeriesInsights/environments/eventsources/ingress/deserialize" | where _ResourceId contains "<your environment name, event source name, or the full event source resource URL>" | where TimeGenerated > ago(5d)
Azure Monitor alerts proactively notify you when important conditions are found in your monitoring data. They allow you to identify and address issues in your system before your customers notice them. You can set alerts on metrics, logs, and the activity log. Different types of alerts have benefits and drawbacks.
When creating an alert rule based on platform metrics, be aware that for Time Series Insights platform metrics that are collected in units of count, some aggregations may not be available or usable.
- See Azure Time Series Insights monitoring data reference for a reference of the logs and metrics created by Azure Time Series Insights.
- See Monitoring Azure resources with Azure Monitor for details on monitoring Azure resources.