Timedora
Free Online Flashcard Deck

2 Monitoring and Alerting Free Online FlashCards

Study 2 Monitoring and Alerting with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

Why should teams set monitoring goals before choosing metrics?

Back

Define operational goals first, such as detecting user-visible failures, finding capacity risks, supporting incident diagnosis, or checking service objectives.

02
Front

How do black-box and white-box monitoring differ?

Back

Black-box monitoring tests the service as users experience it; white-box monitoring measures internal components to help locate causes.

03
Front

What are the four golden signals for a user-facing service?

Back

The four golden signals are latency, traffic, errors, and saturation, which indicates how close a system is to its capacity.

04
Front

Why track latency percentiles instead of only averages?

Back

Latency percentiles reveal slow experiences for some users; averages can hide those delays.

05
Front

What makes logs easier to search and correlate?

Back

Logs are timestamped event records. Structured fields such as time, severity, service, and request or trace identifier make them easier to search and correlate.

06
Front

What do traces reveal in a distributed system?

Back

A trace shows a request's path across services and helps identify where time is spent or errors arise.

07
Front

Why correlate metrics, logs, and traces?

Back

Correlating metrics, logs, and traces provides a more complete view of system behavior than relying on any one signal.

08
Front

What is a dashboard's role during incident response?

Back

A dashboard makes service health understandable at a glance and helps responders move from a symptom toward likely causes.

09
Front

What makes a notification a useful alert?

Back

An alert is a notification that requires a person to act. It should address an urgent problem, affect users or soon do so, and enable a specific response.

10
Front

Why prefer sustained service impact over a brief CPU spike?

Back

Prefer alerting on sustained user-impacting checkout errors or latency rather than paging for one server's brief CPU spike.

11
Front

How should urgent and non-urgent alerts be routed?

Back

Page responders for urgent, actionable problems; route important but non-urgent work to a ticket or review dashboard.

12
Front

How can evaluation windows reduce alert noise?

Back

Use suitable evaluation windows or persistence conditions so brief blips can recover without repeatedly interrupting responders.