uberAgent

Microsoft Azure Monitor (legacy)

May 11, 2026

Contributed by:

C C

This page documents the legacy Microsoft Azure Monitor backend.

Support/Status

Microsoft has announced the deprecation of the HTTP Data Collector API for Azure Monitor, which will no longer function after September 14, 2026. uberAgent uses this API to transmit data to Azure Monitor.

The uberAgent team thoroughly evaluated the newer Logs Ingestion API, intended to replace the HTTP Data Collector API, and found the following issues:

An ingestion model and rate limits that do not scale sufficiently even for moderately-sized uberAgent deployments.
Limitations on the number of data flows per Data Collection Rule and Data Collection Endpoint that are insufficient for uberAgent’s broad range of metrics.
High administrative overhead for customers setting up environments in Azure.

Unfortunately, it must be concluded that the Logs Ingestion API does not meet uberAgent’s technical requirements. This means that Microsoft no longer provides a viable way for uberAgent to send data to Azure Monitor. For this reason, Azure Monitor is no longer supported as a backend for uberAgent.

Migration Guidance

Customers who wish to keep their data in Azure may use Microsoft’s recommended data analytics platform, Microsoft Azure Data Explorer (ADX). Azure supports cross-service KQL queries, which allow an existing Log Analytics workspace to query data stored in an ADX database by using the adx function. Please refer to Microsoft’s documentation for more details.

Customers who want to use different backends may refer to the list of supported uberAgent backends.

Creating the Log Analytics Workspace

The following legacy information is kept for reference for existing deployments:

Navigate to https://portal.azure.com and sign in with your Microsoft account or your Organizational account associated with your Microsoft Azure subscription.
Navigate to the Azure service Log Analytics workspaces and create a new workspace by specifying a unique workspace name, subscription, resource group, location and pricing tier or use an existing workspace linked to your Microsoft Azure subscription.
Open up the Advanced settings > Connected sources menu and note the WORKSPACE-ID and the PRIMARY-KEY.

Configuring uberAgent to Send to Azure Monitor Logs

To configure uberAgent to send its collected data to Azure Monitor Logs the following Receiver configuration settings are required:

Type: OMSLogAnalytics
Protocol: HTTP
Servers: https://WORKSPACE-ID.ods.opinsights.azure.com
RESTToken: PRIMARY-KEY

Example

[Receiver]
Name = Default
Type = OMSLogAnalytics
Protocol = HTTP
Servers = https://WORKSPACE-ID.ods.opinsights.azure.com
RESTToken = SECRET-PRIMARY-KEY
<!--NeedCopy-->

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Microsoft Azure Monitor (legacy)

May 11, 2026

Contributed by:

C C

May 11, 2026

Contributed by:

C C

Microsoft Azure Monitor (legacy)

Support/Status

Migration Guidance

Creating the Log Analytics Workspace

Configuring uberAgent to Send to Azure Monitor Logs

Example

In this article