Software Craft

Static thresholds cause alert fatigue when they are tight and missed incidents when they are loose. Dynamic alerting adapts as the behavior of the system changes. Part of my observability series.

A request crosses many services before it fails. End-to-end visibility shows the whole path, from the interface to the infrastructure, so a team can find the bottleneck. Part of my observability series.

Observability works best when it is designed in from the start. Build the logs, instrumentation, and monitoring hooks with the feature, and use that data to decide what to build next. Part of my observability series.

Metrics, logs, and traces say little alone. Correlation links them with events, configuration changes, and deployments, so a team finds the root cause faster. Part of my observability series.

Metrics show the health of a system. Logs record what happened. Traces show which component is responsible. Together they give a team one view. Part of my observability series.

Dive into the three pillars of observability 2.0 – metrics, logs, and traces – and understand their significance in enabling a comprehensive monitoring strategy.