The number of Locator Service cache flush requests that were unsuccessful for any reason. For example, a request may fail because it was for an invalid cache entry, or the cache may not flush because of an incorrect cache state.
A high count may indicate a problem with the LocatorService cache, or a problem with the connection to CONFIG_DB. For information about the cause, review the event log for errors.
Target | Microsoft.Dynamics.CRM.Common |
Category | PerformanceCollection |
Enabled | True |
Instance Name | CRM LocatorService |
Counter Name | LocatorServiceFailedCacheFlushRequests |
Frequency | 900 |
Alert Generate | False |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | System.Performance.OptimizedDataProvider | Default |
WriteToDB | WriteAction | Microsoft.SystemCenter.CollectPerformanceData | Default |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData | Default |
<Rule ID="Microsoft.Dynamics.CRM.Locator_Service_Failed_Cache_Flush_Requests" Enabled="true" Target="Microsoft.Dynamics.CRM.Common" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>PerformanceCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Performance!System.Performance.OptimizedDataProvider">
<ComputerName>.</ComputerName>
<CounterName>LocatorServiceFailedCacheFlushRequests</CounterName>
<ObjectName>CRM LocatorService</ObjectName>
<InstanceName/>
<AllInstances>false</AllInstances>
<Frequency>900</Frequency>
<Tolerance>0</Tolerance>
<ToleranceType>Absolute</ToleranceType>
<MaximumSampleSeparation>1</MaximumSampleSeparation>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData"/>
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData"/>
</WriteActions>
</Rule>