Bitzu

AZ-400 ยท Analyzing telemetry

Infrastructure and application metrics

CPU, memory, disk and network indicators, saturation and bottleneck reading, usage and application performance metrics (response time, failure rate, dependencies), Metrics Explorer and workbooks.

Key points

  • Infrastructure indicators: CPU, memory, disk, network.
  • Saturated: so heavily used that work queues up; the usual bottleneck.
  • Application indicators: server response time, failed request rate, request volume, dependency call duration.
  • Low CPU with slow responses: a dependency, not the host.
  • Metrics Explorer: metrics over time. Workbooks: charts, queries, text in one shared report.
  • Pre-aggregated metrics stay accurate under SDK sampling.

Source: https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling-classic-api

Practice questions

Single choice

Which indicator most directly describes how quickly a web application answers incoming requests?

  1. Available memory on the host
  2. Server response time
  3. Disk queue length
  4. Network bytes received per second
Show answer

Answer: B. Server response time

Server response time is an application performance metric measured per request. Memory, disk queue and network throughput are host indicators that can contribute to slowness but do not measure it directly.

Select all that apply

Which of these are application performance indicators rather than host infrastructure indicators?

  1. Failed request rate
  2. Free disk space on the volume
  3. Server response time
  4. Dependency call duration
  5. Network adapter output queue
Show answer

Answer: A. Failed request rate, C. Server response time, D. Dependency call duration

Failed request rate, server response time and dependency call duration are measured from the application's own requests and calls. Free disk space and network adapter queue length describe the machine.

True or false

True or false: if average CPU is low, the application cannot have a performance problem.

Show answer

Answer: False

False. An app can be slow while waiting on a database, a remote API, disk or a lock, all of which leave CPU idle. Average CPU also hides short spikes.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-400 topics in this module