Failed Staging Table Diagnostics

Microsoft.ApplicationServer.FailedStagingTableDiagnostics (Diagnostic)

Element properties:

TargetMicrosoft.ApplicationServer.MonitoringStoreConnectedConnection
MonitorMicrosoft.ApplicationServer.FailedStagingTableRowCount
RemotableTrue
Timeout300
Execute On StateError
CategoryCustom
Enabledtrue
AccessibilityInternal

Member Modules:

ID Module Type TypeId RunAs 
GenericStoreReader.PA ProbeAction Microsoft.ApplicationServer.GenericStoreReader.ProbeAction Microsoft.ApplicationServer.StoreAdminAccount

Source Code:

<Diagnostic ID="Microsoft.ApplicationServer.FailedStagingTableDiagnostics" Accessibility="Internal" Enabled="true" Target="MicrosoftApplicationServerLibrary!Microsoft.ApplicationServer.MonitoringStoreConnectedConnection" Monitor="Microsoft.ApplicationServer.FailedStagingTableRowCount" ExecuteOnState="Error" Remotable="true" Timeout="300">
<Category>Custom</Category>
<ProbeAction ID="GenericStoreReader.PA" RunAs="MicrosoftApplicationServerLibrary!Microsoft.ApplicationServer.StoreAdminAccount" TypeID="Microsoft.ApplicationServer.GenericStoreReader.ProbeAction">
<Query>SELECT TOP 1 Id, TimeCreated, ErrorNumber, ArchiveId, Computer, EventSource, ProcessId, TraceLevelId, E2EActivityId FROM [ASFailedStagingTable] ORDER BY Id DESC</Query>
<Description>The following record in FailedStagingTable triggered this monitors unhealthy state.</Description>
<ConnectionStringHash>$Target/Property[Type="MicrosoftApplicationServerLibrary!Microsoft.ApplicationServer.StoreConnection"]/ConnectionStringHash$</ConnectionStringHash>
</ProbeAction>
</Diagnostic>