Event submitted by Event Log Doctor
Event ID:
Heartbeat Monitoring

Starting with EventSentry build, 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.

To enable this functionality, the following SQL query will need to be executed on the EventSentry database:

--Built-In Database (PostgreSQL)
REVOKE ALL ON TABLE eventsentry.essysinfo FROM eventsentry_svc;
GRANT SELECT, UPDATE, INSERT, DELETE ON TABLE eventsentry.essysinfo TO eventsentry_svc;

-- SQL Server
GRANT SELECT ON ESSysinfo (UptimeTimestamp) TO eventsentry_svc

-- MySQL
GRANT SELECT (computer, Uptime, UptimeMax, UptimeTimestamp), INSERT, UPDATE, UPDATE (UptimeTimestamp, lastserverinventoryupdate), DELETE ON essysinfo TO eventsentry_svc

It is also recommended to set the "Refresh uptime every" interval in the "Inventory" System Health package to 5 minutes.

Solution by Event Log Doctor

2016-04-25 14:51:55 UTC

Run the shown SQL commands to give the Heartbeat Agent the ability to query the EventSentry agent status from the database. This is recommended for large installations as well as networks with slow links.

If the Heartbeat Agent cannot query the database for whatever reason, it will revert to the legacy method of querying the EventSentry service status.

If you do not wish to make this change, simply ignore this event or setup an exclusion filter for it.

User Information
Only an Email address is required for returning users.

Hide Name


Additional Links