| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Infrastructure monitoring | IT operations and endpoint | 0% | 26 of 79 | 20% | 5 | under 10 labels · led by Datadog at 28% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Log management | IT operations and endpoint | 0% | 58 of 73 | 40% | 5 | under 10 labels · led by Datadog Log Management at 28% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Observability platforms | IT operations and endpoint | 0% | 64 of 80 | 67% | 3 | under 10 labels · led by Grafana at 27% | newNew since September 2026: not ranked then, 0% now. |
| Telemetry pipelines | IT operations and endpoint | 0% | 83 of 124 | 0% | 1 | under 10 labels · led by OpenTelemetry Collector at 37% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Infra monitoring | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 17 → 26 of 79 |
| Logs | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 23 → 58 of 73 |
| Observability | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 64 of 80, unchanged |
| Telemetry pipelines | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 83 of 124, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-5.4 mini | 0 | 1 | 1 | 0 | 2 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 1 | 1 |
| Perplexity Sonar | 0 | 0 | 0 | 1 | 1 |
| Grok 4.20 | 0 | 0 | 0 | 0 | 0 |
| Mistral Small | 0 | 0 | 2 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 1 | 0 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 0 | 1 | 1 | 2 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 1 | 1 |
| MiniMax M2.5 | 0 | 1 | 0 | 1 | 2 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 1 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“If you're already in a public cloud: Use the native monitoring (CloudWatch, Azure Monitor, Google Operations)” MiniMax M2.5 · Observability · budget prompt · alternative
“cloud-native tools like AWS CloudWatch, Azure Monitor, and Google Cloud Monitoring” Llama 4 Maverick · Infra monitoring · budget prompt · alternative
“best if you're mostly on Microsoft/Azure” GPT-5.4 mini · Logs · paraphrase prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Cloud provider dashboards | Azure Monitor, AWS CloudWatch | Not intuitive; tedious dashboard creation” GLM 4.7 FlashX · Infra monitoring · negative prompt · hard negative
“best when you are already standardized on that ecosystem, but they can be less attractive if you want portability” Perplexity Sonar · Logs · negative prompt · soft negative
“cloud-native log management becomes deceptively expensive as your application scales” Gemini 3.5 Flash · Logs · negative prompt · soft negative
“Best-in-class for Azure, but cross-cloud orchestration often needs extra adapters.” MiniMax M2.5 · Observability · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 21 of the 30 answers that named Azure Monitor and are not a share of its labels.
Forty-six of the forty-six domain citations in answers naming Azure Monitor came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Azure Monitor's own pages state, read September 28, 2026: azure.cn. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Azure Monitor's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Azure Monitor, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Azure Monitor by email, built from the raw record of the edition. It shows: