City app servers for parking, licensing, and inspections write logs only to local disks, so ops cannot search a single incident across the fleet. What observability capability should the municipality configure first?
Select an answer to reveal the explanation.
Short Explanation
Local logs are like sticky notes stuck inside each office—nobody can see the whole story when something breaks. Log collection pulls those notes into one place so you can search an incident across parking, licensing, and inspections without hopping servers. Fleet-wide troubleshooting starts with getting the logs off the box.
Full Explanation
Log collection aggregates logs from distributed sources so operators can query incidents across services and hosts. Leaving logs only on local disks blocks correlation, slows response, and risks loss if a host fails. For Cloud+ observability (3.1), configuring collectors or agents that forward logs to a central platform is the foundational step before retention, alerting, and deeper analysis.