Overview
A client-mode connector for a curated observability / ITSM slice of Azure Monitor:
Default
BASE_ADDRESS is https://YOUR_DCE.ingest.monitor.azure.com. Topics use itsm/azure-monitor/<object>/<verb>. Switch BASE per surface (Logs / Metrics / Query) the same way other multi-host connectors do.
Replace
YOUR_DCE with your Data Collection Endpoint hostname (or use the DCR logsIngestion endpoint). Prefer Hub secrets for Entra client credentials and workspace / DCR / resource identifiers. This template has not been verified against a live Azure subscription. Status remains blocked until an authenticated live smoke succeeds.Basic Syntax
Authentication
Acquire tokens from
https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token. Scopes: https://monitor.azure.com/.default (logs), https://monitoring.azure.com/.default (custom metrics), https://api.loganalytics.io/.default (query). Store tenant / client / secret in Hub secrets (AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET) and resolve via GET SECRET — never commit credentials.
MQTT examples
Logs ingest (JSON array; BASE = DCE):access_token, dcr_immutable_id, stream_name, and api_version (2023-01-01). Expect HTTP 204.
Custom metric (BASE = {region}.monitoring.azure.com):
api.loganalytics.azure.com):
Action Group webhook companion
Azure Monitor Action Groups can deliver Common Alert Schema (or older schemas) to a webhook URL. Package a separateENABLE_SERVER true REST_API connector to receive those POSTs on an MQTT-bound path. That inbound surface is not included in AzureMonitorRestApi.lot.
Sources
- Logs Ingestion API
- Custom metrics REST
- Metrics - Custom - Create
- Logs query API
- API access and authentication
- Action groups
Package
Broker template folder:src/CorefluxCentral/Routes/Templates/RestApiConnectors/azure-monitor/
Deployable file: AzureMonitorRestApi.lot (no ADD METADATA). Hub icon/status: hub-metadata.lot.
