StackExchange.Exceptional

We had a similar experience, so I'm just sharing the path we took. We were using New Relic APM and Server Monitoring through the Microsoft BizSpark benefits for an year or two. We were even ready to pay for their licenses, but New Relic pricing for multi-server use was starkly high for a small tech company like ours. Their product was good, but their focus was more on enterprise customers. After trying out many other commercial products (focusing on .NET Core stack in particular), and keeping long-term scalability and TCO in mind, we decided to utilize some open source solutions. First we tried Bosun[1] (from the Stack Exchange team), but found little progress being made on it. Then, we tried Prometheus[2] collectors for monitoring, Grafana[3] for the dashboards and alerting, and Exceptional[4] for logging. One person got it all working w

We indeed use SQL for errors (though Exceptional has a couple of stores...and you can add a new one). The reason a SQL outage isn't an issue is a) we have other alarms for that, and b) Exceptional will fall back to an in-memory exception queue and flush to the DB when it's available again. In the event of a store loss (file share, SQL server...whatever your store is) then it queues exceptions in memory with rollups to reduce memory usage, and will flush to the store when it's available again. It does a connectivity test every 2 seconds in the event of failure. Exceptional is open source and is the basis for what's used in Opserver...the UI is even very, very similar it's just that Opserver has more features for a multi-application view. You can see the source here: https://github.com/NickCraver/StackExchange.Exceptional