Provides information about security failures.
Assembly: System.Web (in System.Web.dll)
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 class is used when a security operation fails. An example of this is a failed URL authorization for a Web request.
By default, ASP.NET is configured to raise the event for the following features:
File authorization. ASP.NET attempts file authorization only when a Windows Identity is associated with the request. The related event audit code is AuditFileAuthorizationFailure.
URL authorization. This governs unauthorized attempts to access a URL resource. Failed attempts by an anonymous user are not audited, because anonymous authentication failure is acceptable in most circumstances. The related event audit code is AuditUrlAuthorizationFailure.
Generic unhandled or security unhandled conditions. The following is a list of the event codes related to these conditions:
When a event is raised, ASP.NET health monitoring increments the related Audit Failure Events Raised performance counter and then checks the healthMonitoring configuration section to determine whether any providers subscribe to the event. If providers subscribe to the event, ASP.NET dispatches the event to them for processing.
To view the Audit Failure Events Raised performance counter in System Monitor (PerfMon), in the Add Counters window, select ASP.NET from the Performance object drop-down list, select the Audit Failure Events Raised performance counter, and click the Add button. For more information, see Using the System Monitor (PerfMon) with ASP.NET Applications in the IIS documentation on MSDN.
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 deriving from the class, see the Example section.
When formatting your custom event information for display, override the FormatCustomEventDetails method rather than the ToString method. This will avoid overwriting or tampering with sensitive system information.
The following code example demonstrates how to derive from the class to create a custom audit event.
The following configuration excerpt shows how to enable ASP.NET to use the event.
<healthMonitoring enabled="true" heartBeatInterval="0"> <providers> <add name="EventLogProvider" type="System.Web.Management.EventLogWebEventProvider, System.Web,Version=2.0.3600.0,Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> </providers> <eventMappings> <add name="SampleWebFailureAuditEvent" type="SamplesAspNet.SampleWebFailureAuditEvent, webfailureauditevent,Version=1.0.1663.31140, Culture=neutral, PublicKeyToken=0d1fa0f69d94de96, processorArchitecture=MSIL"/> </eventMappings> <rules> <add name="Custom Failure Audit Default" eventName=" SampleWebFailureAuditEvent " provider="EventLogProvider" profile="Default"/> </rules> </healthMonitoring>
Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.