Polylane for Azure: find and fix issues across your subscription
Polylane now checks each production resource in a connected Azure subscription for issues, with or without Azure Monitor alert rules, and writes the fix.
What changed
Polylane now checks each production resource in a connected Azure subscription for issues, without needing an
Azure Monitor alert rule. When it finds one, an investigation traces the cause through your resources, logs and recent changes, and Polylane writes the fix for your review. See Polylane for Azure.
Metric and log checks
Each production resource is checked on a schedule set by its tier. Polylane compares its Azure Monitor metrics with the resource's own history and opens an issue when one moves the wrong way and stays there. For resources that send logs to Log Analytics, each check also reads the error lines, so failures that only show in logs, such as gateway 500s or dropped database connections, are caught too.
A check after each deploy
Deploying an App Service, Function App, Logic App or container app adds a check 15 minutes later, so an issue the deploy introduced does not wait for the next scheduled check. Zip and Kudu deploys count too.
Azure Monitor alerts
When you allow it at connect, Polylane creates Azure Monitor alert rules for production resources and investigates each alert. Your own rules are investigated when they notify the Polylane action group.
Why it matters
Alert rules only cover the failures someone set up in advance, and many Azure failures only show in logs. Checking each resource against its own metrics and logs finds those issues without a rule.
How to use it
- In Polylane, open Settings > Clouds and connect
Azure. Turn on Create alert rules if you want Polylane to add
Azure Monitor alert rules, then choose Deploy on
Azure.
- In the
Azure portal, select the subscription to connect and choose Review + create. You need the Owner role on that subscription.
- Keep the Polylane page open until
Azure confirms the delegation. It usually takes a minute or two.