# Choose whether an Azure Monitor SLI counts requests or time windows

> Should a busy interval carry more weight in the service's reliability measurement?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-164-choose-whether-an-azure-monitor-sli-counts-requests-or-time-windows/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:29:12+00:00
- Modified: 2026-09-10T00:55:35+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Explainer
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Should a busy interval carry more weight in the service's reliability measurement?

## Potentially affected

Azure Monitor service-level indicators configured for service groups; the source identifies service-group creation as preview.

## DSE recommendation

Choose the evaluation population before setting the target percentage: individual requests or qualifying time intervals.

## Article

## Source facts

Azure Monitor request-based SLIs compare good requests with total requests. Window-based SLIs instead compare intervals that meet a quality threshold with all intervals in the compliance period. Microsoft describes request-based evaluation as reflecting per-request success despite uneven traffic, while the window model can smooth brief poor-performance bursts. Setup requires a service group; the prerequisite links to preview service-group creation. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/service-level-indicators-create).

## Applicability

Use this decision when defining what a reliability percentage should represent. The target and time horizon still need an explicit service-level decision; choosing the same percentage does not make two different evaluation populations equivalent.

## DSE recommendation

Choose the evaluation population before setting the target percentage: individual requests or qualifying time intervals. Ask the service owner how a short, heavily loaded incident should influence the measure compared with a quiet interval. Document the intended numerator and denominator for request evaluation, or the qualifying threshold for windows. Keep the rationale beside the SLI so later reviewers do not interpret a window percentage as a request-success percentage.

## Verification

Use representative historical telemetry containing both busy and quiet intervals. Compare the two proposed interpretations and check which answers the approved service question. Inspect the preview for the selected signals, filters and formulas before creating the SLI. Retain the chosen method and the comparison evidence; a target being met under one method should not be reported as a successful result under the other or as proof of every user’s experience.

## Official references

[Microsoft Learn: Service-level indicators](https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/service-level-indicators-create). Source reviewed September 9, 2026.

## Primary reference

- Name: Create service level indicators in Azure Monitor - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/service-level-indicators-create
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose whether an Azure Monitor SLI counts requests or time windows,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-164-choose-whether-an-azure-monitor-sli-counts-requests-or-time-windows/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.