Using Tracked Object Manager in Your Network

The Tracked Object Manager provides the ability to track local and remote objects by means of tracked objects and probes. Tracked objects monitor the state of local entities, such as interfaces. Probes monitor the state of remote entries, such as host servers. Each tracked object or probe is a container governed by a set of rules and configurable attributes used to determine the state of a collection of one or more of their respective entities. The run-time states of the tracked objects and probe are either up or down. Other states display a configuration or initiation state.

The Tracked Object Manager provides its services to client applications. An application must register with the Tracked Object Manager in order to use its monitoring services. When a client application wants to follow the state of a local service, the application registers with a tracked object. If the client application wishes to determine the state of a remote server, it creates a probe session. The Tracked Object Manager is responsible for monitoring the state of the configured objects and reports back to the registered client applications when the state of these objects change.