Creating Heartbeat trigger objects

In Trust Protection Platform, the TLS Protect, Validation Manager, and Discovery Module generate Heartbeat events every 15 minutes to confirm they are running and functional. To facilitate your system maintenance, you can configure Heartbeat Trigger notifications to monitor these Heartbeat events.

To create a Heartbeat Trigger object

Log in to the Trust Protection Platform Administration Console.

NOTE You must have the Create permission to the Notifications folder in the Logging tree.
Select the Logging tree in the Tree drop-down menu.
In the Logging tree, select the Notification Rules folder.
Click Add > Heartbeat Trigger.
In the Log Heartbeat dialog, type the heartbeat trigger name.
Set the Timeout interval.
From the Event drop-down list, select the Log - Heartbeat missed event.
In the Text 1 field, type the text that you want to appear in the Event log. For example, type Missed Timeout.
(Optional) In the Text 2 field, add additional event log information such as the object name.
In the Value 1 field, specify a unique event ID for all Heartbeat Missed events triggered by this Heartbeat Trigger object. For example, type 5 as the event ID.
(Optional) In the Value 2 field, add additional information such as how to fix the problem.
Click Save.
Use the instructions in the next section to configure a Notification Rule for the Log - Heartbeat event missed event.

The following table outlines the configuration settings for Heartbeat Trigger objects.

Heartbeat Trigger Object Configuration Settings
Field	Description
Condition	Defines the Heartbeat Trigger criteria.
Timeout	Maximum number of minutes between each event occurrence. Heartbeat events for the TLS Protect, Validation Manager, and Discovery Module occur every 15 minutes. If the event does not occur within the designated interval, the Venafi Log server generates the Heartbeat Missed event (EventID 00010002, Log - Missed Heartbeat).
Event	Event you want the logging server to monitor. The Discovery Module generates the following Heartbeat event every 15 minutes to confirm it is running and functional: 0007000C,Discovery - Discovery Heartbeat
Disabled	A checkbox to disable the Heartbeat Trigger/
Triggered Event	If the designated event does not occur within the timeout interval, the Log server generates the Heartbeat Missed event (EventID 00010002, Log - Missed Heartbeat). Because the Heartbeat Missed event is generic and does not identify the source component that originally triggered the event, you must use the Text1, Text2, Value1, and Value2 fields defined in the Heartbeat Trigger object to indicate which system component triggered the Heartbeat Missed event so that you can track the event and determine which system component has failed.
Text 1	Information that appears in Text1 field. It can contain any text string up to 255 characters.
Text 2	Information that appears in Text2 field. It can contain any text string up to 255 characters.
Value 1	Information that appears in the Value1 field. It can contain any numeric value up to 32 bits.
Value 2	Information that appears in the Value2 field. It can contain any numeric value up to 32 bits.
General Tab
Permissions	On the Permissions tab, you select the users or groups to whom you want to grant permissions to the current object. Then, you select which permissions you want the users or groups to have. You can also manage object permissions via parent objects, including the root Platform object or the Trust Protection Platform server object (found in the Platforms tree). If you configure Permissions in a parent object, those permissions are inherited by all subordinate objects.