ASP.NET Event Providers in .NET

Generation Denso QR Bar Code in .NET ASP.NET Event Providers

Rather than requiring you to write code to perform any number of different event noti fication mechanisms, the .NET Framework includes several event providers, as described in Table 13-5. Both the events that are built into ASP.NET and custom events that your application generates can be sent through any of these providers.

Description Writes Web event data to the Windows event log. By default, this provider is configured to write all errors to the Windows event log. Security operation errors are logged under the event name Failure Audits and all other errors are logged under the event name All Errors. To read event log data, you can view data using the Windows Event Viewer or read event log data pro grammatically.

Logs Web event data to a Microsoft SQL Server database. By default, this provider logs data to the SQL Server Express database in the Web applica tion s App_Data folder. It does not subscribe to any events by default.

13

Description Passes Web events to Windows Management Instrumentation (WMI), converting them to WMI events. By default, this provider does not subscribe to any events. Sends an e-mail message when Web events are raised. By default, these providers are not configured and do not subscribe to any events. Passes event data to the ASP.NET page tracing sys tem. By default, this provider is not configured and does not subscribe to any events. Tracing provides you with the ability to start and stop event tracing sessions, to instrument applications to provide trace events, and to consume trace events. You can use the events to debug an application and perform capacity and performance analysis.

Additionally, you can create your own custom event providers by inheriting from the WebEventProvider or BufferedWebEventProvider classes. Custom event providers can log events to a custom log file, send event data to third-party monitoring systems, and meet other specific requirements that might be provided by your IT department.

For more information about creating custom event providers, read Extending ASP.NET Health Mon itoring at http://msdn2.microsoft.com/en-us/ms228095.aspx.

ASP.NET includes many different types of events that can be sent through any of the event providers. These events are listed in Table 13-6.

Description Represents a significant event in the lifetime of an ASP.NET application. Application lifetime events include events such as application startup and shut down events. If an application is terminated, you can determine why by viewing the related eventmessage field. Serves as the base class for all ASP.NET health-mon itoring audit events. Provides information about ASP.NET authentica tion failures. Provides information about successful authentica tion events. Serves as the base class for all the health-monitoring error events. Serves as the base class for the ASP.NET healthmonitoring events. Provides information about errors caused by prob lems with configuration or application code. An example is the error issued by ASP.NET when an error is found in a page. Provides information about security failures. Serves as a timer for the ASP.NET health-monitoring system. These events are raised at an interval defined by the heartbeatInterval attribute of the <healthMonitoring> configuration section. Serves as the base class for events that carry applica tion and process information. Defines the event that carries information about Web-request errors.

WebAuditEvent WebAuthenticationFailureAuditEvent WebAuthenticationSuccessAuditEvent WebBaseErrorEvent WebBaseEvent WebErrorEvent

13

Description Serves as the base class for events providing Webrequest information. Provides information about successful security events. An example of this is a successful URL authorization for a Web request. Provides Web application view state failure infor mation.

Additionally, you can create your own custom Web events by deriving a class from one of the base event classes shown in Table 13-6, such as WebManagementEvent or WebAuditEvent.