</>SkillRecallRECALL WHAT YOU KNOW
Prepare for an interviewExplore Library
Cloud & DevOps FundamentalsMonitoring, Logging & Observability

20 items

1

Availability SLI Calculation Bug

Code Quiz
2

Understanding SLIs and SLOs

Quiz
3

Emitting the Three Telemetry Pillars

Code Quiz
4

Choosing the Right Observability Signal

Quiz
5

Azure Monitor Alert Query Bug

Code Quiz
6

Azure Monitor & Log Analytics Basics

Quiz
7

Correlating the Three Pillars

Code Quiz
8

Distinguishing Metrics, Logs, and Traces

Quiz
9

Prometheus Instance-Down Alert Bug

Code Quiz
10

Choosing the Right Metric Type

Code Quiz
11

Prometheus and Grafana Roles

Quiz
12

The Three Pillars of Observability

Quiz
13

Alerting, SLIs and SLOs Basics

Slides / Video
14

The Three Pillars of Observability

Slides / Video
15

SLI, SLO, and Alerting Basics

Flashcard
16

The Three Pillars of Observability

Flashcard
17

Azure Monitor & App Insights Basics

Slides / Video
18

Azure Monitor & Application Insights Basics

Flashcard
19

Alerting, SLIs, SLOs & Dashboards

Slides / Video
20

SLIs, SLOs & Alerting Basics

Flashcard
Code QuizAdvanced

Azure Monitor Alert Query Bug

Spot the time-filter mistake in a Log Analytics KQL query used for an Azure Monitor alert.

Codekusto
// Alert: fire when there are too many HTTP 500s in the last 5 minutes
AppRequests
| where TimeGenerated < ago(5m)
| where ResultCode == "500"
| summarize FailureCount = count() by bin(TimeGenerated, 1m)
| where FailureCount > 10

What is the bug in this Log Analytics alert query?