Health Monitoring : 3

 I need to do is configure web.config open up the web.config file here and I'll go over to the web health monitoring.config this configuration information this health monitoring element of the web.config file let you specify the SQL Web event provider class you can configure this provider and specify the events that you want to monitor in the rules section 2 in this case which is defined in application lifetime events roll specifying all events as well as the provider that is created appear as little bit more to talk about for configuring and using health monitoring the health monitoring section that we just let that contains only two of the elements required for configuration the providers that were going to use in this case a SQL Server and the rules that we want to use there's.

 A third required element called event mappings and this is inherited from the root web.config file the event name value all events that we sign the web.config file refers to one of the event mappings in the root web.config file slots and look at that section or have opened the root web.config file and I scroll down to the health monitoring section. We'll see the built-in event mappings which are named categories of event data based on the event type in a range of that codes the providers listed here are the three built-in providers for sending event data to the Windows event log or to Debbie on my Windows management instrumentation the role specify provider and event mapping and configuration options that you can use to throttle the flow of data and you can use profiles to centralize the configuration of those throttling options by specifying sets of providers rules and event mappings you determine which event data is recorded and where it is recorded.

So scroll down a bit so we have profiles rules and then we have various event mappings settle to find within the root web.config file which means available to all ASP.net applications so sickle look at the view offense page I'll govern the design view and you can see that we just have a simple grid with the SQL data source the SQL data source is configured to read from the ASP net Web event events so can take a look at the source for that and you can see the select statement that is going to be executed in order to read that data and open everything in order by the event in descending order we also delete command defined so that you can delete all existing events in order to clear out the database will use the code behind the page and all we have is within the page unload event is going to clean up all the old events that are contained within the database and to do that all we need to do is call the delete method of the web events data source) run the application and you can see the most recent event data recorded within the database when you close the page then it deletes all of the old events

Summary

If you have a website that has to be highly reliable and scalable monitoring itself with weather events is just what the doctor ordered with performance data in a SQL Server database you can analyze it to your heart's content to find and fix problems before anyone else notices the such as a user who find your site down with the.net is monitoring stuff shouldn't you be to