Administration > Monitor Administration > SiteScope Data Collector Configuration > Managing SiteScope > SiteScope Health > SiteScope Health Monitor Reference > Log Event Health Monitor
Log Event Health Monitor
This monitor is designed to check the error.log file for the local SiteScope installation. You can edit the counters, the update frequency and the display name for this monitor type. Click Get Counters to edit the counters selected for the monitor. You can use the Advanced Settings to disable the monitor individually as well as selecting other options as shown on the monitor properties panel.
The status thresholds for this monitor are based on the counters selected. The counters for this monitor type are listed in the table below.
Note: Only the first 15 selected counters will be configured and monitored. A maximum of 10 measurements can be used as status threshold criteria for alerting.
Log Event Monitor Counters
The following tables lists all the available counters for this health monitor.
|
Counter
|
Description
|
|
skipped #1
|
A monitor has skipped its scheduled run once
|
|
skipped #2
|
A monitor has skipped its scheduled run two times
|
|
skipped #3
|
A monitor has skipped its scheduled run three times
|
|
skipped #4
|
A monitor has skipped its scheduled run four times
|
|
skipped #5
|
A monitor has skipped its scheduled run five times
|
|
SiteScope shutting down
|
SiteScope has been shut down
|
|
Reached the limit of processes in the process pool
|
The number of processes requested from the process pool exceeds the number of processes available in the pool
|
|
Error. data reporter failed to report chunk of data
|
There was a fault in the transfer of SiteScope monitor measurement data to Mercury Business Availability Center
|
|
Error. config reporter failed to report chunk of data
|
There was a fault in the transfer of SiteScope configuration data to Mercury Business Availability Center Monitor Administration
|
|
Error. Topaz failed to process data
|
Mercury Business Availability Center reported a fault in processing data sent from SiteScope
|
|
Error. CacheSender. Got to the max number of cached files
|
SiteScope has reached the maximum number of cached data file awaiting transfer to Mercury Business Availability Center. This may occur if data transfer between SiteScope and Mercury Business Availability Center has been interrupted.
|
|
Error. CacheSender. Got to the max old dir size
|
SiteScope has reached the maximum directory size for cached data file awaiting transfer to Mercury Business Availability Center. This may occur if data transfer between SiteScope and Mercury Business Availability Center has been interrupted.
|
|
Topaz SEVERE
|
Mercury Business Availability Center reported a data transfer or processing fault with a status of SEVERE
|
Status thresholds for this monitor are set on counters listed in the table above.