Operations Guide

Legacy Monitoring

Informatica recommends the use of Automatic Monitoring with user applications and daemons, and the use of the Monitoring Collector Service (MCS) to collect and record statistics. However, these features have not always been available (MCS was introduced in UM version 6.14).

Informatica will continue to support these older "legacy" monitoring methods in their current state and functionality. However, as we continue to develop and enhance the monitoring data and their collection and storage, these legacy methods will not always be similarly enhanced. Informatica recommends users of these legacy methods to migrate to automatic monitoring and MCS.

The legacy methods are:

- Self-Monitoring Applications using statistics API.
- "Web monitors" of the Store and DRO daemons.
- Binary Daemon Statistics of the Store and DRO daemons.
- Monitoring UM with the lbmmon API.

# Self-Monitoring Applications <-

User applications can use the statistics API to sample UM library statistics. The application would typically record the library statistics, along with the applications own statistical data, and possibly raise alarms.

This method is considered "legacy". Informatica recommends users migrate to Automatic Monitoring with user applications and daemons, and Monitoring Collector Service (MCS) to collect and record statistics.

C programs wishing to self-monitor should use the APIs:

- lbm_context_retrieve_src_transport_stats() - see Example lbmmsrc.c.
- lbm_context_retrieve_rcv_transport_stats() - see Example lbmrcv.c.
- lbm_context_retrieve_stats().
- lbm_event_queue_retrieve_stats().

Java and .NET programs should use the APIs:

- LBMContext.getSourceStatistics()
  - see Example lbmmsrc.java.
- LBMContext.getReceiverStatistics()
  - see Example lbmmrcv.java.
- LBMContext.getStatistics().
- LBMEventQueue.getStatistics().