Thanks, that lets me see the "dead ducks" nicely.
Do you know of away to add an "Actions" so that I can have it start it up on that host when this is triggered?
Following that URL and another Link http://www.viktorious.nl/2012/05/10/esxi-5-syslogger-stops-logging-collective-restart-using-powercli/ there, I see that this PowerCLI will work. Any way to get that into the trigger?
foreach ($esxhost in (Get-Cluster -Name $cluster | Get-VMHost )){
Write-Host "ESX: $esxhost"
$esxcli = Get-EsxCli -VMhost $esxhost
$esxcli.system.syslog.reload()
}
I have VMware vSphere PowerCLI installed on my "Windows" vCenter box. Or if it can be done within the alarm itself.
--thanks a lot.