Without historical baselines, every CPU spike on the city’s GIS servers looks like an emergency. What should ops establish to make metrics and alerting meaningful?
Select an answer to reveal the explanation.
Short Explanation
Baselines are knowing what “normal rush hour” looks like on the freeway—without them every bump feels like a crash. Once GIS CPU has a normal range, real emergencies stand out from routine peaks. Raw thresholds with no history turn ops into permanent crisis mode.
Full Explanation
Baselines describe expected metric behavior over time so anomalies are interpreted in context. Without them, alerting on absolute values creates false emergencies and hides true regressions. Cloud+ observability guidance emphasizes baselining so metrics and alerts reflect meaningful deviation rather than raw readings alone.