Nice article, I would be curious how it is implemented and how you setup the rules for alerting.
I'm working with Microsoft's Semantic Logging Application Block to standardize error logging and auditing across all my .NET apps. It utilizes the built-in Event Tracing for Windows (ETW) to capture events written by any application, and writes them to a destination of your choice (db, file, etc). .NET 4.5 includes a new EventSource class that I inherit from, and simply call WriteEvent() and the message goes off to ETW. Reference: http://blogs.msdn.com/b/agile/archive/2013/02/07/embracing-s...
I would like to add heartbeats to my design, in addition to just error logging, tracing and http auditing.
I'm working with Microsoft's Semantic Logging Application Block to standardize error logging and auditing across all my .NET apps. It utilizes the built-in Event Tracing for Windows (ETW) to capture events written by any application, and writes them to a destination of your choice (db, file, etc). .NET 4.5 includes a new EventSource class that I inherit from, and simply call WriteEvent() and the message goes off to ETW. Reference: http://blogs.msdn.com/b/agile/archive/2013/02/07/embracing-s...
I would like to add heartbeats to my design, in addition to just error logging, tracing and http auditing.