History data collection requests

You can use TEMS REST services to interact with history collection and history collection configurations.

To make history data available for reporting, you must collect the history data for the appropriate products and attributes. To control what data is collected, you must configure the history collection.

History collection gathers useful metrics about your managed systems. A history collection configuration defines what historical data is collected for individual attribute groups and specifies from which managed systems to collect data, how frequently to collect the data, where to store it for the short term, and whether to save data long-term to a data warehouse. History collection configurations determine what historical data is available for retrieval and reporting.

Note: In the Tivoli Enterprise Portal, you use the History Collection Configuration window to access history collection configuration definitions.

The following types of history data collection requests are available using TEMS REST services:

Retrieving history data that has already been collected
Managing what data is collected
Retrieving history collection status information
Starting and stopping history data collection

Note: History collection configurations are stored as internal UADVISOR situations. A UADVISOR situation is a special form of situation that is created for internal product use and is not visible in the Tivoli Enterprise Portal. The name of a UADVISOR situation is in the format UADVISOR_xxxxx. Commonly, Kpp and tablename appear in the name.