ProbeWatch messages

During normal operations, the probe generates ProbeWatch messages and sends them to the ObjectServer. These messages tell the ObjectServer how the probe is running.

The following table describes the raw ProbeWatch error messages that the probe generates. For information about generic ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC14-7530).

Table 1. ProbeWatch messages
ProbeWatch message	Description	Triggers/causes
`Probewatch: Connection Failure`	The probe failed to connect to the target system in the specified period.	The remote server might be unavailable because of a network outage. Check the log files for more information.
`Probewatch: Received heartbeat`	The probe received a heartbeat message from the event source.	The occurrence of a heartbeat message.
`Probewatch: Client connected`	A client has connected to the probe.	A client successfully connects to the probe.
`Probewatch: Client disconnected`	A client disconnected from the probe.	A client disconnected from the probe.
`Probewatch: Logout attempted`	The probe attempted to logout from the target server.	The occurrence of a logout attempt.
`Probewatch: Logout successful`	The probe has successfully logged out from the target server.	The occurrence of a successful logout.
`Probewatch: Logout failed`	The probe has failed to logout from the target server.	The occurrence of an unsuccessful logout.
`Probewatch: Login attempted`	A login attempt by the probe or client.	A client attempted to login to the probe (server) or the probe (client) attempted to login to the target server.
`Probewatch: Login failed`	A login failed.	A client failed to login to the probe (server) or the probe (client) failed to login to the target server.
`Probewatch: Login successful`	A login attempt was successful.	A client successfully logged in to the probe (server) or the probe (client) successfully logged in to the target server.