The latest articles on DEV Community by Anmol Jain (@ajain). https://dev.to/ajain https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3899186%2F25a698fe-11d4-4bf2-83f2-cdc758874078.jpg https://dev.to/ajain en Anmol Jain Fri, 01 May 2026 19:58:22 +0000 https://dev.to/ajain/free-tool-to-analyze-nestjs-logs-errors-latency-rpm-5b66 https://dev.to/ajain/free-tool-to-analyze-nestjs-logs-errors-latency-rpm-5b66 <p>Debugging production NestJS logs is painful.</p> <p>You end up scrolling through thousands of lines trying to:</p> <ul> <li>identify errors </li> <li>find slow APIs </li> <li>understand what failed and where </li> </ul> <p>So I built a simple tool to fix this.</p> <h2> What it does </h2> <p>Paste or upload NestJS logs (default logger, Pino, or Winston). It:</p> <ul> <li>Extracts errors with file names and line numbers </li> <li>Highlights slow routes (p95/p99 latency) </li> <li>Calculates request rate (RPM) and error % </li> <li>Aggregates errors with counts and timestamps </li> <li>Generates a shareable link (7 days) </li> </ul> <h2> Example output </h2> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fifyzyf8lyf9zsgf6prjh.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fifyzyf8lyf9zsgf6prjh.png" alt="Latency distribution across endpoints with p95 and p99 metrics highlighting slow APIs" width="800" height="502"></a></p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fkotzz61yuc30eu2dmrpz.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fkotzz61yuc30eu2dmrpz.png" alt="Timeline showing errors, HTTP failures, and high latency events along with slow route summary" width="800" height="520"></a></p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fb8folq8vrzgjh9of0i80.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fb8folq8vrzgjh9of0i80.png" alt="Aggregated error table with file names, line numbers, and HTTP status code distribution" width="800" height="483"></a></p> <h2> Try it </h2> <p><a href="https://micro-tools.co/tools/dev/log-analyzer" rel="noopener noreferrer">https://micro-tools.co/tools/dev/log-analyzer</a> </p> <p>No signup. No ads. Just paste logs and get insights.</p> <h2> Feedback </h2> <p>Would this be useful in your workflow?</p> nestjs node logging devtools