Why use an HTTP module to monitor ASP.NET health or vice versa?

Question

I came across this question several times, you need to do some performance testing (query request time, load time, etc.) or track unused exceptions. The answers usually come down to writing an HTTP module, connecting to specific events and registering them somewhere, or using the built-in health monitoring?

Why should we use one over the other? What are the pros and cons?

Answer 1

You can write your own HTTP module that registers an unhandled exception, or you can use ASP.Net health monitoring. I think you do not know that you can write your own ASP.Net health monitoring provider, which allows you to send e-mail, register in the database, or do whatever you want with the exception.

The great professional for using a custom provider is that it naturally supports eliminating buffering in groups to reduce spam and performance issues. If you use your own HTTP module for this, you need to write more code that will only do the same, but it has the disadvantage that it costs time and can be error prone.

, , , healthMonitoring xml- node, HttpModules.

: ASP.Net Health?