Home
  •  

Valid Host No APM Agent

Microsoft.SystemCenter.Apm.ValidHostNoAPMAgentMonitor (UnitMonitor)

Monitor that watches for .NET Framework installed on a system with an Operations Manager health service that does not have the APM service installed

Knowledge Base article:

Summary

This monitor changes state when a server hosting .NET Framework is found that does not have the Operation Manager APM agent installed.

Causes

When the Operation Manager agent was first installed in this server, .NET Framework was not present and the APM agent was not installed. .NET Framework has been added to the server and it is now a valid target for .NET Monitoring.

Resolutions

Repair the Operations Manager agent on the target server to install the APM agent.

Element properties:

TargetMicrosoft.SystemCenter.HealthService
Parent MonitorSystem.Health.ConfigurationState
CategoryConfigurationHealth
EnabledFalse
Alert GenerateFalse
Alert Auto ResolveTrue
Monitor TypeMicrosoft.SystemCenter.Apm.ValidHostNoAPMAgentMonitorType
RemotableFalse
AccessibilityPublic
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SystemCenter.Apm.ValidHostNoAPMAgentMonitor" Accessibility="Public" Enabled="false" Target="SC!Microsoft.SystemCenter.HealthService" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="false" Priority="Normal" TypeID="Microsoft.SystemCenter.Apm.ValidHostNoAPMAgentMonitorType" ConfirmDelivery="false">

  <Category>ConfigurationHealth</Category>

  <OperationalStates>

    <OperationalState ID="InvalidHost" MonitorTypeStateID="InvalidHost" HealthState="Success"/>

    <OperationalState ID="ValidHost" MonitorTypeStateID="ValidHost" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

    <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</ComputerName>

    <Frequency>14400</Frequency>

    <WindowsVersion>6.0</WindowsVersion>

  </Configuration>

</UnitMonitor>