Skip to content

A query using max() finds short term latency spikes #36746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 20, 2019
Merged

A query using max() finds short term latency spikes #36746

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a2c16df
A query using max() finds short term latency spikes
sbonds Aug 8, 2019
c27ead5
Remove example per team request
sbonds Aug 20, 2019
c8531bc
Merge branch 'master' into patch-2
ktoliver Aug 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions articles/azure-monitor/platform/data-ingestion-time.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,8 +94,11 @@ Heartbeat
| summarize percentiles(E2EIngestionLatency,50,95), percentiles(AgentLatency,50,95) by Computer
| top 20 by percentile_E2EIngestionLatency_95 desc
```

If you want to drill down on the ingestion time for a specific computer over a period of time, use the following query which also visualizes the data from the past day in a graph:

The preceding percentile checks are good for finding general trends in latency. To identify a short-term spike in latency, using the maximum (`max()`) might be more effective.

If you want to drill down on the ingestion time for a specific computer over a period of time, use the following query, which also visualizes the data from the past day in a graph:


``` Kusto
Heartbeat
Expand Down