Log Web Event Provider Class
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Implements an event provider that logs ASP.NET health-monitoring events into the Windows Application Event Log.
public ref class EventLogWebEventProvider sealed : System::Web::Management::WebEventProvider
public sealed class EventLogWebEventProvider : System.Web.Management.WebEventProvider
type EventLogWebEventProvider = class inherit WebEventProvider
Public NotInheritable Class EventLogWebEventProvider Inherits WebEventProvider
The following configuration file excerpt shows how to specify a provider of type EventLogWebEventProvider to handle success audit events. The EventLogWebEventProvider and the failure audit health-event types to monitor are configured by default. To monitor the success audits, you need to configure them, as shown in the example code.
<healthMonitoring enabled="true" heartbeatInterval="10"> <rule> <add name="Success Audits Default" eventName="Success Audits" provider="EventLogProvider" profile="Default" minInterval="00:01:00" /> </rule> </healthMonitoring>
ASP.NET health monitoring allows production and operations staff to manage deployed Web applications. The System.Web.Management namespace contains the health-event types responsible for packaging application health-status data and the provider types responsible for processing this data. It also contains supporting types that help during the management of health events.
The EventLogWebEventProvider, the failure audit, and the error health-monitoring events are configured (enabled) by default. This means that the failure audit and the error health-monitoring events are logged in the Windows Application Event Log by default.
In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the
healthMonitoring configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see How to: Implement the Health Monitoring Custom Provider Example.
Gets a brief, friendly description suitable for display in administrative tools or other user interfaces (UIs).(Inherited from ProviderBase)
Gets the friendly name used to refer to the provider during configuration.(Inherited from ProviderBase)
Determines whether the specified object is equal to the current object.(Inherited from Object)
Moves events from the provider's buffer into the event log.
Serves as the default hash function.(Inherited from Object)
Gets the Type of the current instance.(Inherited from Object)
Sets the initial values for this object.
Creates a shallow copy of the current Object.(Inherited from Object)
Processes the event passed to the provider.
Performs tasks associated with shutting down the provider.
Returns a string that represents the current object.(Inherited from Object)