Tag archive
Keep Netdata's stock alerts for disk space, memory pressure, OOM kills and failed systemd units...
A broker node ran out of disk on a Thursday morning and stopped accepting writes. We found out from a...
A nightly customer-support pipeline needs failure alerting without a risky cutover: polling logs and...
Support kept forwarding the same complaint: the site hangs for half a minute, several times a day,...
Short answer: for a logistics SaaS rolling out a pricing rule behind a flag, capture application...
Short answer: combine a scheduled budget read with an enforced spending ceiling. The read gives a...
Run the scheduled budget review and the hard stop together, and use the cap as a floor rather than as...
Short answer: use a native log alert when it can express the policy; use a cursor-based Node.js...
Most pages don't matter. Learn to build alerts that are symptom-based, severity-tiered, and tied to SLO burn rate, so the pager only fires when a huma
Short answer: error tracking can preserve and query the failures behind a customer-support incident,...
Short answer: for app logging with alerts in a property-management experiment, compare managed tools...
Short answer: polling a metrics API can provide adequate failure alerting for a small gaming service,...