SystemEDGE tracks the values of various integer-based MIB objects (counters, gauges, and so on) over time and store these values for later retrieval. This functionality, commonly called history sampling, reduces the amount of management station polling across the network. The agent provides this functionality through two SNMP MIB tables:
History Control table
Class: empireHistoryCtrlEntry
Instance: value of empireHistoryCtrlDescr attribute for the specific History Control table entry
History table
Class: empireHistoryEntry
Instance: value of empireHistorySampleIndex attribute for the specific History table entry
The History Control table contains parameters that describe the data that is sampled and stored in the History table. Each row in the control table defines a specific data collection function by assigning values to the parameters (column objects) of the table. One or more rows (stored samples) in the History table are associated with that single control row.
Each control table row is assigned a unique index value (empireHistoryCtrlIndex). A row defines the data collection function by specifying the object instance that you want to sample, how often to sample (in multiples of 30 seconds), and the number of samples to keep (buckets). Associated with each data-collection function (row of the control table) is a set of rows of the History table. Each row of the History table, also named bucket, holds the value of the specified MIB object gathered during one sampling interval.
As each sampling interval occurs, the agent adds a row in the History table with the same empireHistoryIndex value as other rows for this data collection function. This new row corresponds to the single row in the History Control table and has an empireHistorySampleIndex value one greater than the SampleIndex of the previous sample.
For more information about the attributes in these tables and using them for history collection, see the chapter "History Collection."
|
Copyright © 2013 CA.
All rights reserved.
|
|