logs / observability / devops

  submitted by   <a href="https://www.reddit.com/user/AMC_au"> /u/AMC_au </a> <br/> <span><a href="https://coderlegion.com/14672/the-36-signals-we-use-to-predict-deployment-failures-before-they-happen">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1skca17/the_36_signals_we_use_to_predict_deployment/">[comments]</a></span>

The piece argues that without observability, “success” is just unchallenged silence: systems that produce no logs, metrics, or errors let failures masquerade as correct behavior. It highlights that parts of software can execute or fail without emitting signals, making success and failure indistinguishable and causing teams to default to treating silence as correctness. The article warns this complacency undermines reliability, complicates debugging, and hides silent data loss or degraded performance. It urges engineering teams to prioritize observability—structured logs, metrics, traces, alerts—and design for detectable outcomes so correctness can be validated rather than assumed.

  submitted by   <a href="https://www.reddit.com/user/fagnerbrack"> /u/fagnerbrack </a> <br/> <span><a href="https://allan.reyes.sh/posts/keeping-secrets-out-of-logs/">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1rvjgvc/keeping_secrets_out_of_logs/">[comments]</a></span>

Log messages are mostly for the people operating your software | Hacker News Hacker News new | past | comments | ask | show | jobs | submit login Log messages are mostly for the people operating your software ( utcc.utoronto.ca ) 5 points by todsacerdoti 1 hour ago | hide | past | favorite | discuss help Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact Search: