6.6

Table Of Contents
Reviewing the Applications Log
The Applications Log helps when troubleshooting the protected application environment.The Applications Log
provides information about the behavior of all protected applications and includes events such as task status
changes, rule triggering, task outputs, and application warnings. Use this log to troubleshoot application errors.
The order that entries are displayed can be sorted either ascending or descending by clicking the column title.
Filtering Application Log Entries
vCenter Server Heartbeat can filter Applications Log files to limit the events displayed. By default, all events
are displayed in the Applications Log file.
Procedure
1 Right-click an event in the Applications Log and select Filter or click Filter in the Applications Log pane
of the Applications: Summary page.
2 In the upper section, clear the event types you do not want to view.
3 To limit the date and time range, select Only show events from and edit the date or time range.
4 Click OK.
The Application Log events are filtered to meet the selected criteria.
Managing Services
The Applications: Services page displays all services that you or plug-ins specify and the services related to
them by dependency. vCenter Server Heartbeat manages services that depend on protected services (started
and stopped) but not monitored (not restarted if stopped by some external agency). vCenter Server Heartbeat
monitors protected services (restarted if stopped) but not managed (not stopped if protected applications are
stopped).
Adding a Service
To protect a service that was not automatically added by vCenter Server Heartbeat during installation, the
service must be added via the vCenter Server Heartbeat Console and be in a Running state.
Procedure
1 Right-click on any service and select Add from the menu or click Add on the Applications: Services page
to invoke the Add Service dialog.The Name drop-down list contains a list of all currently running unprotected
services.
2 Select the service and set the values for Target State on Active and Target State on Passive. Normally
the Target State on Active is set to Running and the Target State on Passive is set to Stopped.
Note Setting the target state for both the active and passive nodes to Running can cause the service to
place a lock on some files preventing synchronization from completing.
56 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide