WebEventBufferFlushInfo Class
Contains the parameters defining the flush buffer characteristics.
Namespace: System.Web.Management
Assembly: System.Web (in System.Web.dll)
The WebEventBufferFlushInfo type exposes the following members.
| Name | Description | |
|---|---|---|
 | Events | Gets the events collection in the current message. |
| EventsDiscardedSinceLastNotification | Gets the number of events dropped since the last notification. |
| EventsInBuffer | Gets the number of events in the buffer. |
| LastNotificationUtc | Gets the date and the time of the last notification. |
| NotificationSequence | Gets the message sequence in the current notification. |
| NotificationType | Gets the current notification type. |
| Name | Description | |
|---|---|---|
| Equals(Object) | Determines whether the specified object is equal to the current object. (Inherited from Object.) |
| GetHashCode | Serves as a hash function for a particular type. (Inherited from Object.) |
| GetType | Gets the Type of the current instance. (Inherited from Object.) |
| ToString | 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.
The WebEventBufferFlushInfo class defines values that identify the buffer's current status. An instance of the class is passed as a parameter to the ProcessEventFlush method that processes the messages that have been buffered. ASP.NET health monitoring calls this method when the flushing of the buffer is required. This is determined by the parameters defined by the bufferModes element in the healthMonitoring configuration section.
| Note |
|---|
By design, the buffering mechanism might drop some events in order to keep pace with the incoming events. It is up to the user to adjust this mechanism by properly modifying the bufferModes element in the healthMonitoring configuration section. |
| Topic | Location |
|---|---|
| How to: Implement the Health Monitoring Custom Provider Example | Building ASP .NET Web Applications |
| How to: Implement the Health Monitoring Custom Provider Example | Building ASP .NET Web Applications |
The following code example shows how to use the WebEventBufferFlushInfo class. This code example is part of a larger example provided for the BufferedWebEventProvider class.
// Processes the messages that have been buffered. // It is called by the ASP.NET when the flushing of // the buffer is required. public override void ProcessEventFlush( WebEventBufferFlushInfo flushInfo) { // Customize event information to be sent to // the Windows Event Viewer Application Log. customInfo.AppendLine( "SampleEventLogWebEventProvider buffer flush."); customInfo.AppendLine( string.Format("NotificationType: {0}", GetNotificationType(flushInfo))); customInfo.AppendLine( string.Format("EventsInBuffer: {0}", GetEventsInBuffer(flushInfo))); customInfo.AppendLine( string.Format( "EventsDiscardedSinceLastNotification: {0}", GetEventsDiscardedSinceLastNotification(flushInfo))); // Read each buffered event and send it to the // Application Log. foreach (WebBaseEvent eventRaised in flushInfo.Events) customInfo.AppendLine(eventRaised.ToString()); // Store the information in the specified file. StoreToFile(customInfo, logFilePath, FileMode.Append); }
Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
