Navigation:  Monitoring with EventSentry > Heartbeat Monitoring >

Defining a Host as a Router

If you are monitoring routers in addition to other network devices such as servers that are located behind that router, then you can avoid unnecessary heartbeat alerts by assigning the "router" flag to a monitored computer.

Currently, each group may have one router assigned to it, and you cannot make a host a router for all monitored hosts.

When a host is designated as a router in a group, then alerts written to the event log will be suppressed for all hosts in that group, with the exception of the host which is designated as a router. Information that is written to the database is not affected by this setting, and the heartbeat status and history page will still show the actual network status.

The table below shows which type of alerts will be generated when a router becomes unavailable: