How to Use Clients with Operations Sentinel

This subsection describes some general ideas for incorporating clients into your Operations Sentinel environment.

Using Alerts

Operations Sentinel Console displays alerts to the operator through its Alerts windows. The alerts can also be sent to a client for the attention of another user, or to archive them. The client that receives the alert event can use the information in any way.

Using Log Files

Operations Sentinel includes a logging capability that automatically logs information from the systems you are monitoring. In addition, you can use a client to send information to a log file. If you are running an application on a managed system, and you want to track data produced by that application, you can send it to that system’s log. The client sends the information through the Event Server using the Event Server API, where it is written to the specified log file.

Although a client can register to receive log events, the client only receives those log events that were sent by user-supplied API clients. It does not receive the standard log events recorded by Operations Sentinel logging, because these events are not communicated using event reports.

Sending Information to Operations Sentinel Console

You can use a client to send information to Operations Sentinel Console that changes an attribute value or deletes an instance of an object.

Sending Commands to Hosts

You can use a client to submit a command to a managed system that has an active console connection. Command Security (discussed in the Operations Sentinel Administration and Configuration Guide) lets the administrator allow or prevent cross-system commands from an API client.