Event Log

<< Click to Display Table of Contents >>

Navigation:  Monitoring with EventSentry > Heartbeat Monitoring >

Event Log

Event Log 32 n t

The following events are logged by the Heartbeat Agent with the Heartbeat Monitoring event category.

 

Event ID

Event Description

Example / Description

11000

Host %1 (%2) changed its PING status from %3 to %4. The reason for the status change was: "%5".

Host www.competition.com (BigBrother) changed its PING status from OK to ERROR. The reason for the status change was: "100% packets missing".

11001

Host %1 (%2) changed its AGENT status from %3 to %4. The reason for the status change was: "%5".

Host DC1 (DomainControllers) changed its AGENT status from OK to ERROR. The reason for the status change was: "Agent Stopped".

11002

Host %1 (%2) changed its TCP status from %3 to %4. The reason for the status change was: "%5".

Host mail.yourdomain.com (DMZ) changed its TCP status from OK to ERROR. The reason for the status change was: "Unable to establish a TCP connection (10060) (TCP Port: 25)".

11005

The EventSentry Heartbeat monitor is ready and will now start monitoring the configured hosts.

The EventSentry Heartbeat monitor is ready and will now start monitoring the configured hosts.

11006

The EventSentry Heartbeat agent was unable to find the required HTML template files in %1\Heartbeat. Please make sure that the following files exist in %1\Heartbeat:

 

template_status_start.html

template_history_start.html

template_end.html

image subdirectory

 

These files are optional if you are already logging heartbeat information to a database.

The EventSentry Heartbeat agent was unable to find the required HTML template files in C:\Program Files\Heartbeat. Please make sure that the following files exist in C:\Program Files\Heartbeat:

 

template_status_start.html

template_history_start.html

template_end.html

image subdirectory

 

These files are optional if you are already logging heartbeat information to a database.

 

11007

The EventSentry Heartbeat agent was unable to find the required HTML template files and is not configured to log heartbeat status information to a database. The heartbeat agent will only notify you of host status changes through the event log.

The EventSentry Heartbeat agent was unable to find the required HTML template files and is not configured to log heartbeat status information to a database. The heartbeat agent will only notify you of host status changes through the event log.

 

11008

The database action specified for the heartbeat monitoring service is invalid and database logging has been disabled. Please review the configuration and restart the heartbeat monitoring service.

The database action specified for the heartbeat monitoring service is invalid and database logging has been disabled. Please review the configuration and restart the heartbeat monitoring service.

 

11009

The Heartbeat Monitor detected that the EventSentry service is currently not running. If the EventSentry service is not running, then event log alerts generated by the Heartbeat Agent cannot be forwarded to a notification.

 

You can disable this check under "Global Options -> Heartbeat".

This event indicates that the EventSentry agent is not currently running, and thus not able to dispatch any heartbeat alerts.

11010

The EventSentry Heartbeat service encountered an unrecoverable error and will now automatically restart.

 

If you see this message on a regular basis, then set the "Debug Level" under "Heartbeat" to "High" and contact support@netikus.net the next time this message is generated.

It is acceptable to observe this event on occasion, but a frequent occurrence (e.g. once a day) should be reported to our support team for investigation.

11011

Scanning of host %1 was forcefully aborted because the scan duration (%3) exceeded the maximum allowed time (%2 seconds).

 

Review the monitoring settings of this host, and optionally disable Agent and/or TCP checks on this host.

In order to monitor all configured hosts in a timely fashion and thus dispatch alerts as soon as they occur, the heartbeat monitor limits the time it takes to monitor a single remote host. If this time is exceeded, scanning of the remote host is aborted and this error is logged.

 

Review this error and optionally exclude certain features from being monitored (e.g. SNMP, agent status or TCP).

11012

Scanning of host %1 was interrupted %4 consecutive times because the scan duration (%2) exceeded the maximum allowed time (%3 seconds). TCP Port and/or SNMP scanning may be incomplete on this host.

Indicates that a host scan had to be aborted multiple, consecutive times and that its hosts status may be incomplete.

11014

SNMP monitoring of host %1 has failed %2 consecutive times and is now disabled. To re-enable SNMP monitoring of host %1, restore SNMP connectivity and restart the EventSentry Heartbeat Monitor service.

Indicates that SNMP monitoring for a host has been disabled because the heartbeat monitor was unable to obtain any SNMP data from the remote host.

11015

SNMP or agent monitoring of host %1 has failed %2% of the time over the last %3 seconds and is now disabled. To re-enable SNMP and/or agent monitoring of host %1, restore full connectivity to the remote host, locate the host in the management console and click the "Retry" button in the summary view.

Indicates that SNMP monitoring has been permanently disabled and needs to be manually re-activated through the management console.

11016

The following error occurred while communicating, or attempting to communicate with database action "%1": "%2". Please verify that the database is accessible and the database is on the latest schema.

Indicates an error while trying to store data in the EventSentry database. Run the configuration assistant to ensure that all database are on the latest schema.

11017

The connection with database action "%1" has been reestablished, the database is no longer offline.

Indicates that a previously unavailable database is now available.

11018

Starting with EventSentry build 3.2.1.28, the heartbeat agent can query the EventSentry database to determine a remote agent status, instead of querying the remote agent status using the Windows API. This can drastically improve the monitoring speed and is recommended for networks consisting of 50 or more Windows hosts.

Click here for more information.

11019

Monitoring of the remote EventSentry agent on host %1 has been unsuccessful %2 times in a row. Remote agent monitoring will now be disabled on host %1.

Monitoring of a remote agent failed too many times and is now disabled.

11020

The heartbeat agent will monitor the following host using SNMP:

 

Host: %1

SNMP Version: %2

System Description: %3

The heartbeat agent will monitor the following host using SNMP:

 

Host: 192.168.73.43

SNMP Version: 2c

System Description:ProCurve J9021A Switch 2810-24G, revision N.15.09, ROM N.12.03 (/sw/code/build/bass(bh7))

11050

The PING status of host %1 (%2) remains at %4 due to error "%5".

The PING status of host mail.somedomain.com (Heartbeat Hosts) remains at ERROR due to error "100% packets missing".

11051

The AGENT status of host %1 (%2) remains at %4 due to error "%5".

The AGENT status of host DC1 (DomainControllers) remains at ERROR due to error "Agent Stopped".

11052

The TCP status of host %1 (%2) remains at %4 due to error "%5".

The TCP status of host mail.yourdomain.com (DMZ) remains at ERROR due to error "Unable to establish a TCP connection (10060) (TCP Port: 25)".