This subsection describes specialized agents that provide the Operations Sentinel server with information about the systems on which they reside. For these agents, the term “control” refers to control of the agent rather than control of the monitored system on which it resides.

Event Server API Clients

Site-supplied Event Server API client programs, running on any of the systems on which the API is available, can supply event reports to the Operations Sentinel server. They can (transparently) send event reports to either the primary or the secondary Operations Sentinel server, using the capabilities of the API, which only requires identification of the primary and secondary servers through environment variables. The API library automatically handles switching from one server to the other.

Switching from the Primary to Secondary Operations Sentinel Server

Switching from the primary to the secondary Operations Sentinel server is automatic for API clients.

If you have modified the default filter policy on the primary Operations Sentinel server, you have to define the same filter policy or make the same modifications to the default filter policy on the secondary server. Otherwise, a different filter policy becomes active on the secondary server when the switch from primary to secondary occurs.

Summary

The following table summarizes the resiliency issues for agents, clients, and interfaces.

*By initiating two instances of an API client program and specifying distinct Operations Sentinel primary servers for each of them, you can create a concurrent monitoring environment.