New Relic's integrations include an integration for reporting your Microsoft Azure Time Series Insights metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported.
Features
New Relic gathers metrics data from Azure Monitor for the Azure Time Series Insights service. Azure Time Series Insights can easily scale up or down based on the amount of data being ingested and queried. This ensures that you have the resources you need to handle any spikes in data volume.
Using New Relic, you can:
- View Azure Time Series Insights data in pre-built dashboards.
- Run custom queries and visualize the data.
- Create alert conditions to notify you of changes in data.
Activate integration
Follow standard Azure Monitor integration procedure to activate your Azure service in New Relic infrastructure monitoring.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
New Relic queries your Azure Time Series Insight services through the Azure Monitor integration according to a default polling interval.
Find and use data
To explore your integration data, go to one.newrelic.com/infra > Azure > (select an integration).
Metric data
This integration collects the following metric data.
Azure Time Series Insights metrics
Metric | Description |
|---|---|
| Count of bytes read from all event sources. |
| Count of invalid messages read from all Event hub or IoT hub event sources. |
| Count of messages read from all Event hub or IoT hub event sources. |
| Difference between the sequence number of last enqueued message in the event source partition and sequence number of messages being processed in Ingress. |
| Difference between the time that the message is enqueued in the event source and the time it is processed in Ingress. |
| Total size of events successfully processed and available for query. |
| Count of flattened events successfully processed and available for query |
| Maximum number of properties used allowed by the environment for S1/S2 SKU and maximum number of properties allowed by Warm Store for PAYG SKU. |
| Number of properties used by the environment for S1/S2 SKU and number of properties used by Warm Store for PAYG SKU. |