Getting Started

Managing endpoint heartbeats in ServicePulse

ServicePulse relies on heartbeat messages sent from the heartbeat plugin to indicate whether an endpoint is active or inactive. The main dashboard shows a heartbeat icon which will indicate if there are any inactive endpoints.

Heartbeats icon with inactive endpoints

Click this icon to go to the endpoints overview. This page shows a list of active and inactive endpoint instances. Each endpoint instance shows when the most recent heartbeat from that instance was received.

Endpoints overview page

Heartbeats may be shown for each endpoint instance, or for each logical endpoint. Use the "Display" dropdown to change between displaying endpoint instances and logical endpoints.

The list of endpoints can be sorted or filtered using the sort dropdown and the filter textbox on the right side of the page.

Sort and filter Entpoinds

Hiding endpoints

By default, each new endpoint discovered by ServicePulse is monitored for heartbeats. If the endpoint is not sending heartbeats (either because it is offline or because it does not have the heartbeats plugin installed) it will immediately be marked as inactive.

Heartbeat monitoring for endpoint instances can be configured in the configuration tab of the Heartbeats page.

Configuration page

Setting the endpoint to "Off" will prevent it from appearing on the endpoints overview screen and from affecting the dashboard.

Removing endpoints

When an endpoint has been decommissioned and should no longer be displayed in ServicePulse it can be removed. From the Endpoint Heartbeats screen, click the trash bin icon next to an endpoint's name to remove it from ServicePulse. The trash icon is only visible when displaying endpoint instances. It is not shown when displaying logical endpoints.

Remove endpoint