# production-debugging Published articles for production-debugging. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## From slow tests to slow production: Debugging with Stackprof DevFeed: [From slow tests to slow production: Debugging with Stackprof]() Original publisher: [Read original article]() Published: 2026-08-13T00:00:00Z Content type: tutorial Language: en Sources: [Aha! Engineering Blog]() Topics: [debugging](), [Tooling](), [RSpec](), [Databases]() Tags: [ci](), [cpu-time](), [database](), [debugging](), [logs](), [overhead](), [performance](), [production-debugging](), [profiling](), [rspec](), [snapshots](), [tests](), [timing]() ### AI overview An investigation into tests that became six times slower traces the stall to code generating example data and Active Record callbacks. The article explains using Stackprof with RSpec to profile the test, including I/O time, and reports that the test spent 71% of its time sleeping. ### Source excerpt One morning, a developer announced in our Slack channel that some tests were failing on our main branch. The cause of the failures was not obvious. No recent PRs seemed related, and neither the code nor the tests had changed in a long time. The test ## Using Claude and custom tools to streamline production support debugging DevFeed: [Using Claude and custom tools to streamline production support debugging]() Original publisher: [Read original article]() Published: 2026-06-22T00:00:00Z Content type: opinion Language: en Sources: [Aha! Engineering Blog]() Topics: [Claude](), [Tooling](), [debugging](), [Command-line interface]() Tags: [claude](), [cli](), [debugging](), [production-debugging](), [workflows]() ### AI overview An Aha! engineer describes using Claude with a custom production-debugging skill to support customer tickets. The skill links to filtered logs and provides tools for configuration inspection, query analysis, and record history, while customer data is kept out of Claude. ### Source excerpt Every seven weeks or so, each Aha! engineer takes a week of support rotation. I caught myself doing something dumb during my last one. A ticket came in. I clicked over to our production log viewer, narrowed the time range, and started piecing togeth ## Using the OSI Model for Effective Production Issue Debugging DevFeed: [Using the OSI Model for Effective Production Issue Debugging]() Original publisher: [Read original article]() Author: Kamal Kumar Published: 2025-08-28T17:37:45Z Content type: tutorial Language: en Sources: [Housing.com]() Topics: [debugging](), [networking](), [Network](), [Routing (disambiguation)](), [Server](), [Authentication](), [Encryption](), [configuration](), [business logic](), [Framework]() Tags: [analysis](), [apis](), [authentication](), [configuration](), [debugging](), [devops](), [errors](), [firewalls](), [load](), [mapping](), [network](), [osi-model](), [production-debugging](), [production-issue](), [rca](), [root-cause-analysis](), [routing](), [servers](), [sre](), [tcp](), [troubleshooting](), [udp](), [web]() ### AI overview This tutorial explains how to use the seven-layer OSI model to structure root cause analysis for production alerts. It recommends checking lower layers for network and gateway errors, and higher layers for application and client errors, including connectivity, routing, logs, APIs, authentication, and configuration. ### Source excerpt In production environments, debugging alerts can sometimes feel like finding a needle in a haystack. Over the years, I've found the OSI (Open Systems Interconnection) model to be a reliable guide during Root Cause Analysis (RCA) of production issues. What is the OSI Model? The OSI model is a conceptual framework that standardizes the functions of a telecommunication or computing system into seven layers: Physical Layer -- Hardware, cables, switches Data Link Layer -- MAC addresses, switches, network topology Network Layer -- IP addressing, routing Transport Layer -- TCP/UDP, ports, session reliability Session Layer -- Session management, authentication Presentation Layer -- Data translation, encryption Application Layer -- APIs, web servers, applications How I Use OSI Layers in RCA: When I debug production alerts, I follow different approaches depending on the type of error: Network / Gateway Errors (e.g., 502, 504): These errors usually indicate communication issues between services. I start from the bottom layers (Physical -> Network -> Transport) to check connectivity, firewalls, routing, or load balancers. Application / Client Errors (e.g., 500, 503, 404): These errors generally originate from the application or business logic. I start from the top layers (Application -> Presentation -> Session) to check service logs, APIs, authentication issues, or configuration problems. Why this approach works: Following the OSI model provides a structured, layer-by-layer method for troubleshooting, ensuring that we don't miss low-level network issues or high-level application errors. It helps reduce mean time to resolution (MTTR) and improves the quality of RCA reports. Takeaway: The OSI model is not just a theoretical concept -- it's a practical tool that can guide engineers through complex production debugging. Next time you face a tricky alert, try mapping it to the OSI layers, and you might find the root cause faster than you think. Using the OSI Model for Effective Production Issue