You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AzureMonitorLogsTool is a production-ready tool that queries Azure Log Analytics via the REST API, but it has no user-facing documentation. Every other major integration (Datadog, Grafana, Elasticsearch, Coralogix, etc.) has a matching docs/<name>.mdx file — Azure Monitor is missing one.
Context
The tool (app/tools/AzureMonitorLogsTool/) requires three credentials:
workspace_id — the Log Analytics Workspace ID (from Azure portal)
access_token — an Azure AD access token (OAuth2 Bearer) with Data.Read permission on the workspace
endpoint — defaults to https://api.loganalytics.io
It accepts KQL queries and enforces a max result limit of 200 rows.
What to write
Create docs/azure-monitor.mdx following the structure of an existing integration doc (e.g., docs/coralogix.mdx or docs/betterstack.mdx). Include:
Overview — what Azure Monitor Log Analytics is, what the tool retrieves
Prerequisites — Azure subscription, Log Analytics Workspace, service principal with Log Analytics Reader role
Getting credentials — step-by-step: how to find the Workspace ID, how to generate an access token (Azure AD app registration + client credentials flow)
Configuration — how to add the integration in opensre (env vars or opensre configure wizard), with an example config block
Verification — how to confirm the integration is working (opensre doctor or equivalent)
Example KQL queries — 2–3 practical examples (e.g., fetch recent errors, count by severity)
Troubleshooting — common errors (401 Unauthorized, empty results, wrong endpoint)
Acceptance criteria
docs/azure-monitor.mdx created and follows the structure of existing integration docs
Covers prerequisites, credential setup, configuration, and verification
At least two KQL query examples included
Troubleshooting section covers 401 and empty-result scenarios
Summary
AzureMonitorLogsToolis a production-ready tool that queries Azure Log Analytics via the REST API, but it has no user-facing documentation. Every other major integration (Datadog, Grafana, Elasticsearch, Coralogix, etc.) has a matchingdocs/<name>.mdxfile — Azure Monitor is missing one.Context
The tool (
app/tools/AzureMonitorLogsTool/) requires three credentials:workspace_id— the Log Analytics Workspace ID (from Azure portal)access_token— an Azure AD access token (OAuth2 Bearer) withData.Readpermission on the workspaceendpoint— defaults tohttps://api.loganalytics.ioIt accepts KQL queries and enforces a max result limit of 200 rows.
What to write
Create
docs/azure-monitor.mdxfollowing the structure of an existing integration doc (e.g.,docs/coralogix.mdxordocs/betterstack.mdx). Include:Log Analytics Readerroleopensre configurewizard), with an example config blockopensre doctoror equivalent)Acceptance criteria
docs/azure-monitor.mdxcreated and follows the structure of existing integration docsReferences
docs/coralogix.mdx,docs/betterstack.mdx,docs/elasticsearch.mdxapp/tools/AzureMonitorLogsTool/__init__.py