Monitoring on Ghafoor's Personal Blog

Debug With Logging Module

noreply@example.com (AG Sayyed) — Thu, 13 Nov 2025 14:28:51 +0000

This document explores debugging Python programs using the logging module, covering log levels (DEBUG, INFO, WARNING, ERROR, CRITICAL), configuration options, file output, custom formatters, handlers, and best practices for production-grade logging that replaces print statements with structured, filterable log messages.

Introduction

Imagine working on an e-commerce site where business growth brings increasing customers and unexpected errors. While print() statements have been the go-to debugging strategy, they now flood the console with messages, making it hard to discern critical issues from routine operations. A more robust solution is needed to track, categorize, and diagnose issues effectively.

Crashing Programs

noreply@example.com (AG Sayyed) — Thu, 13 Nov 2025 09:59:07 +0000

This document explains how to troubleshoot and debug crashing programs, focusing on quick workarounds, monitoring strategies, and long-term fixes to prevent recurring issues.

Introduction

When faced with a crashing program, the first step is to find a quick workaround to restore functionality. For example, if a database server crashes due to insufficient disk space, adding an extra hard drive can resolve the issue temporarily. However, long-term solutions are essential to prevent recurrence.

Proactive Practices

noreply@example.com (AG Sayyed) — Tue, 11 Nov 2025 18:21:25 +0000

This document describes proactive practices to reduce incidents and simplify troubleshooting: automated testing and CI, test environments and canary deployments, centralized logging and monitoring, ticket automation, documentation, and capacity planning.

Why Proactive Practices Matter

Bugs and failures are unavoidable. Proactive practices reduce their frequency and impact by catching issues early and providing better diagnostic information when problems occur.

Problem Area	Proactive Practice	Benefit
Code regressions	Unit and integration tests + CI	Detects bugs before deployment
Deployment risk	Test environments and canary releases	Limits blast radius
Incident diagnosis	Centralized logging	Faster root-cause analysis
Silent failures	Monitoring and alerting	Detects issues before users report them
Repetitive requests	Ticket templates and automation	Saves triage time
Knowledge gaps	Documentation and runbooks	Consistent on-call response

Automated Testing and Continuous Integration

Automated tests serve as a safety net that catches regressions early. Continuous integration (CI) runs tests on every change, ensuring immediate feedback.