A silent memory spike with zero log entries revealed a 2.4M-restart rsyslog loop
A network engineer running a containerized lab noticed a brief 130 MB memory spike across four Arista cEOS routers on a Grafana dashboard, with no corresponding log entries to explain it. Initial…
Read the full articleYou might also wanna read
Understanding FreeBSD RAM reporting: Why htop, btop, and fastfetch show different memory usage
I spent a whole month researching FreeBSD's kernel's virtual memory system to understand why tools like htop, btop and fastfetch report diff
Stop Guessing Why Your Pods Are Crashing
Kubernetes dashboards often mask a systemic infrastructure failure. When a critical Java service fluctuates and restarts, the post-mortem of
LinkedIn Engineers Diagnose Kernel Lock Contention Behind Recurring Database Freezes
Off-CPU eBPF profiling was triggered instantly during brief database feed outages to capture blocked threads and identify root cause when lo
briefly.co·1mo ago
Understanding Metastable Failures: Self-Sustaining System Performance Issues
I’ve written about metastable failures before. The topic has been picked up by a few different teams since the, all analyzing metastable fai
Restartable Sequences: A Linux Kernel Feature for Lock-Free Thread-Safe Programming
All languages will change to express restartable sequences, and all software will be rewritten to use them.
justine.lol·1mo agoLogs told me something broke. Traffic showed me what.
Capture production traffic and store it in your own Elasticsearch with Speedscale BYOC. Pull it locally with es-gather.py and reproduce bugs
Comments
Sign in to join the conversation.
No comments yet. Be the first.