Provides the base functionality for creating event providers that require buffering.
Assembly: System.Web (in System.Web.dll)
Gets a value indicating the buffering mode used by the provider.
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.)
Gets a value indicating whether the provider is in buffered mode.
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)
Moves the events from the provider's buffer into the event log. (Overrides WebEventProvider::Flush().)
Serves as the default hash function. (Inherited from Object.)
Sets the initial values for this object.(Overrides ProviderBase::Initialize(String^, NameValueCollection^).)
Processes the event passed to the provider.(Overrides WebEventProvider::ProcessEvent(WebBaseEvent^).)
Processes the buffered events.
Performs tasks associated with shutting down the provider.(Overrides WebEventProvider::Shutdown().)
Returns a string that represents the current object.(Inherited from Object.)
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.
If you want to customize the health-event processing, you can derive from theclass to create your own custom buffered provider.
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.
The following code example shows how to derive from theclass to create a custom provider that writes the configured events to a local file for which appropriate access rights must be granted.
The following configuration file excerpt shows a healthMonitoring configuration section that enables ASP.NET to use the custom provider defined above to process all health-monitoring events.
<healthMonitoring heartBeatInterval="0" enabled="true"> <bufferModes> <add name ="Custom Notification" maxBufferSize="10" maxFlushSize="5" urgentFlushThreshold="10" regularFlushInterval="Infinite" urgentFlushInterval="00:00:30" maxBufferThreads="1" /> </bufferModes> <providers> <clear/> <add name="SampleBufferedWebEventProvider" type="SamplesAspNet.SampleBufferedWebEventProvider, bufferedwebeventprovider, Version=1.0.1785.14700, Culture=neutral, PublicKeyToken=d31491bf33b55954, processorArchitecture=MSIL" buffer="true" bufferMode="Custom Notification" /> </providers> <profiles> <add name="Custom" minInstances="1" maxLimit="Infinite" minInterval="00:00:00" /> </profiles> <rules> <clear /> <add name="Custom Buffered Web Event Provider" eventName="All Events" provider="SampleBufferedWebEventProvider" profile="Custom" /> </rules> </healthMonitoring>
Available since 2.0
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.