Q: You ssh to a Linux box to check some logs manually via `less /var/log/syslog`. There are millions of lines. How do you find lines containing "error" and view the lines immediately around them without leaving `less`?
Inside less I would:
less shortcuts.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Logs tell you what happened, metrics tell you where to look, and distributed traces pinpoint the exact slow component. The interviewer is testing: Command line skills for quick observability, less shortcuts.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Inside less I would:
- Press
/and typeerrorand press Enter to search forward. - Use
nto jump to the next match, andNto jump to previous match. - The lines immediately around the match are visible because
lessdisplays the page containing the match.
Remediation & Permanent Safeguards
If I wanted to exit less and output this to another file, I'd use grep -C 5 "error" /var/log/syslog > errors.txt (where -C 5 gives 5 lines of context before and after the match).
- Press / and type error and press Enter to search forward.
- Use n to jump to the next match, and N to jump to previous match.
- The lines immediately around the match are visible because less displays the page containing the ...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability Linux check High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
- Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability Linux check Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
- Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability Linux check Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
- Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability Linux check Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.