A readiness HTTP probe hits /healthz every few seconds, and the app logs every probe as INFO, drowning useful traffic logs. What is the most appropriate application-side response?
Select an answer to reveal the explanation.
Short Explanation
Probe chatter is like a smoke detector chirping every minute—you quiet the chirp, you do not rip out the detector. Tone down logging on the health path. Keep the readiness probe doing its job.
Full Explanation
Noisy probe logging is best handled by adjusting application log levels or filters for the health endpoint while leaving readiness checks in place. Removing readiness reduces traffic-safety signals; discarding all stdout or deleting logs from a probe command destroys observability and is unsafe. CKAD-focused maintenance keeps health checks intact and makes signal easier to find.