Previous Topic: History CollectionNext Topic: State Management Model

CA SystemEDGE User Guide › Concepts › Monitoring Architecture › History Collection › How History Collection Works

How History Collection Works

The SystemEDGE agent carries out history collection instructions as follows:

  1. You create an entry in the History Control table of the Systems Management Empire MIB to monitor a MIB attribute over a specified time interval.

    Note: For more information about creating history collection entries, see the chapter "History Collection."

    The agent requires a restart to recognize changes to the sysedge.cf file unless you use CA Virtual Assurance. If you make an entry and deploy the changes through CA Virtual Assurance, the agent performs a warm start and begins reading the entry while it is running.

  2. The agent polls the attribute according to a specified poll interval and collects the attribute information into the History table (sliding window). When the specified number of samples is reached, the oldest sample is dropped.