Our .NET app goes down while CPU/RAM look fine - what are we missing in monitoring?
retained text
<!-- SC_OFF --><div class="md"><p>Hi everyone,</p> <p>I would like to hear how experienced DevOps engineers approach monitoring for large public-facing applications.</p> <p>We have a .NET e-commerce platform with:</p> <p>- ASP.NET Core MVC + Angular</p> <p>- SQL Server</p> <p>- Elasticsearch (~10M products)</p> <p>- RabbitMQ</p> <p>- IIS hosting</p> <p>- Multiple public domains/subdomains</p> <p>- Heavy SEO crawling and unknown bots</p> <p>One thing we learned is that monitoring only CPU, memory, and disk is not enough.</p> <p>We have experienced situations where:</p> <p>- CPU and RAM looked normal, but the application was slow</p> <p>- The server was reachable, but users experienced downtime</p> <p>- TCP exhaustion caused issues</p> <p>- Elasticsearch had problems affecting search performance</p> <p>- Bots generated a lot of unnecessary traffic</p> <p>- Slow requests were not obvious from infrastructure metrics</p> <p>I would like to know what metrics and alerts you consider essential for this type of system.</p> <p>Some things I think are important:</p> <p>Application level:</p> <p>- Request rate (RPS)</p> <p>- Response time (p50/p95/p99)</p> <p>- HTTP status codes (4xx/5xx)</p> <p>- Slow endpoints</p> <p>- Exception rate</p> <p>- Thread pool starvation</p> <p>- GC pauses</p> <p>- .NET runtime counters</p> <p>- Memory allocations</p> <p>IIS / Web server:</p> <p>- Current connections</p> <p>- Request queue length</p> <p>- Worker process health</p> <p>- Application pool recycling</p> <p>- Failed requests</p> <p>- Connection errors</p> <p>Network:</p> <p>- TCP connections</p> <p>- TIME_WAIT count</p> <p>- Connection failures</p> <p>- Bandwidth usage</p> <p>- Top clients/IPs</p> <p>- Suspicious user agents</p> <p>Elasticsearch:</p> <p>- Cluster health</p> <p>- JVM memory pressure</p> <p>- Heap usage</p> <p>- Search latency</p> <p>- Query failures</p> <p>- Slow queries</p> <p>- Unassigned shards</p> <p>- Disk usage</p> <p>SQL Server:</p> <p>- CPU</p> <p>- Blocking queries</p> <p>- Deadlocks</p> <p>- Query duration</p> <p>- Connection pool usage</p> <p>- Wait statistics</p> <p>RabbitMQ:</p> <p>- Queue length</p> <p>- Consumer count</p> <p>- Message processing time</p> <p>- Dead letters</p> <p>- Memory usage</p> <p>Security / traffic:</p> <p>- Requests to suspicious paths:</p> <p>- /.env</p> <p>- /.git</p> <p>- wp-admin</p> <p>- Bot traffic percentage</p> <p>- High-frequency clients</p> <p>- Rate limit violations</p> <p>My question:</p> <p>If you were responsible for operating a public .NET application like this, what dashboards and alerts would you consider mandatory?</p> <p>Also, what are some metrics you discovered were extremely valuable only after a production incident?</p> <p>I am especially interested in real-world experience rather than a theoretical checklist.</p> <p>Thanks!</p> </div><!-- SC_ON -->   submitted by   <a href="https://www.reddit.com/user/No-Card-2312"> /u/No-Card-2312 </a> <br /> <span><a href="https://www.reddit.com/r/devops/comments/1vye5h9/our_net_app_goes_down_while_cpuram_look_fine_what/">[link]</a></span>   <span><a href="https://www.reddit.com/r/devops/comments/1vye5h9/our_net_app_goes_down_while_cpuram_look_fine_what/">[comments]</a></span>
document fetched 2026-08-26 05:58 · canonical https://reddit.com/r/devops/comments/1vye5h9/our_net_app_goes_down_while_cpuram_look_fine_what