Incidents

What each incident does and the log signature that gives it away.

Articles in this section

• DDoS floodThe DDoS flood is the first incident in SysAdmin Crisis: traffic from non-customer addresses and a bandwidth bar going red. Learn its log signature.
• Memory leakA memory leak in SysAdmin Crisis: one process on one machine that never gives memory back. Learn its log signature and how to tell it apart.
• Disk fullA disk full incident in SysAdmin Crisis: usage crosses 90%, then writes fail at 100%. Learn the log signature and why the ways out are not equal.
• Database lock pile-upA database lock pile-up in SysAdmin Crisis: web servers look healthy while latency climbs. Learn the log signature and how to tell it apart from others.
• OverheatingOverheating in SysAdmin Crisis is a hardware fault software cannot fix, with a thermal shutdown waiting at 95 °C. Learn the signature and how to respond.
• Runaway scheduled jobA runaway cron job in SysAdmin Crisis: a backup starts around three in the morning and pins the CPU at 100% until stopped. Learn the log signature.
• Certificate expiryCertificate expiry in SysAdmin Crisis: one early warning log line, then TLS handshakes that stop working. Learn its signature and how to tell it apart.