AIS Analytics
Correlation-id tracer for Azure Log Analytics
The same tracer, aimed at a Log Analytics workspace instead of Cosmos DB. Paste a correlation id and see every step it touched — it works out which column ties the steps of one flow together straight from the data, then draws where that value got to and where it didn't. An empty lane is as meaningful as a full one.
Free for personal, educational and non-profit use. Commercial use — including a solo consultant on client work — requires a licence. Every build is produced by release CI and served from mayorana.ch.
The macOS build is signed with an Apple Developer ID and notarized, so it opens with a normal double-click.
Read the release notesHow AIS Analytics compares
Only the things AIS Analytics is strong at are listed. The others do plenty it doesn't — this table is about why you would pick it.
| Feature | AIS Analytics | Log Analytics (KQL) | Application Insights transactions | Turbo360 BAM |
|---|---|---|---|---|
| Correlation column inferred from the data, with its evidence | Fixed to operation_Id | You define tracked properties | ||
| One id followed across the workspace without writing KQL | A query per table, or a union | App Insights tables only | Instrumented flows only | |
| Works on Logic Apps diagnostics and custom log tables | By hand | |||
| "Not arrived yet" told apart from "never on this path" |
Compared in October 2026 from each product's public documentation. Something out of date? Tell us
Claude skill
Lets Claude help you with AIS Analytics: how it works, the known errors and their fixes, and a bug report you review before sending it yourself.
How to install it
- claude.ai or the Claude app: Customize → Skills → + → Create skill → Upload a skill, then choose the .zip. “Code execution and file creation” must be on in Settings → Capabilities.
- Claude Code: unzip it into ~/.claude/skills/, so that the skill ends up in ~/.claude/skills/ais-analytics/.
Overview
The same problem as tracing through Cosmos DB, in the place most Azure integration telemetry actually lands: a Log Analytics workspace with more tables than anyone queries regularly.
Paste a correlation id. AIS Analytics works out from the data which column ties the steps of one flow together, then follows that value across the workspace and lays the result out as a timeline.
As with the Cosmos DB tracer, an empty lane carries as much information as a full one — it tells you which step never logged, which is usually the step that broke.
What it does
Column inference from data
Determines which column correlates the steps of a single flow by looking at the workspace, not at a configuration file you maintain.
Workspace-wide trace
One correlation id followed across the tables that matter, without composing a KQL query per table.
Timeline of steps
Every step the value touched, in order, so where time was spent is visible at a glance.
Two kinds of nothing, told apart
A lane with no rows is shown rather than omitted, and the view distinguishes a step the value has not reached yet from one that was never on its path — the difference between waiting and broken.
Requirements
- macOS on Apple Silicon, Windows, or Linux x86_64
- Azure CLI signed in (az login) — the app uses your existing session rather than its own login
- An Azure Log Analytics workspace and read access to it
Built with
Rust · Dioxus · Azure Log Analytics
What's new
Version 0.1.35, released 6 October 2026. AIS Analytics ships often; every version and what it changed is listed on the release notes page.
Read the release notesLicence
Source-available under the PolyForm Noncommercial License 1.0.0: free for personal use, learning, research and hobby projects, and for charities, schools, universities and government institutions. Companies using it for work buy a licence.
Source
The source is public and readable. Fork it and rebrand it — the name and logo are trademarks and are not covered by the licence.
View on GitHubQuestions
Do I need to know KQL?
No. Writing the queries is what the tool removes. Knowing KQL helps you interpret the tables, but you do not write anything to get a trace.
How is this different from AIS Tracing?
Same tracer, different backend. AIS Tracing reads an Azure Cosmos DB account; AIS Analytics reads a Log Analytics workspace. Teams that use both usually run both.
Does it modify the workspace?
No. It only runs read queries.
Questions about this tool?
Ask about a commercial licence for your team, report an issue, or tell us what is missing. We read every message.
Get in touch