Step 9: Configure historical data collection

Edit online

Historical data collection is an optional feature that is enabled through the Tivoli® Enterprise Portal or the OMEGAMON® enhanced 3270 user interface.

The tasks required to enable historical reporting can be performed at any time after you have verified your installation. If you enable historical data collection, the Tivoli Enterprise Monitoring Server sends requests to monitoring agents at a specified interval to collect and store data samples. The collected historical data can be displayed in workspaces in the user interfaces, warehoused for in-depth analysis and long-term data reporting, used as a data source for OMEGAMON Data Provider, and exported to third-party tools for reporting and analysis.

OMEGAMON Web UI supports historical visualizations through Tivoli Enterprise Monitoring Server REST services (TEMS REST API). To view historical data in the starter dashboards, you must enable historical data collection using either the Tivoli Enterprise Portal or the enhanced 3270UI. For a complete list of available dashboards for OMEGAMON agents and the corresponding attribute groups that require history collection, refer to the OMEGAMON Web UI documentation.

Notes:
  • Not all historical data that is displayed in the Tivoli Enterprise Portal can be displayed in the enhanced 3270UI, and not all the near-term history displayed in the enhanced 3270UI can be displayed in the Tivoli Enterprise Portal.
  • The enhanced 3270UI cannot display data from the Tivoli Data Warehouse (TDW), and you cannot configure the Warehouse Proxy agent or the Summarization and Pruning agent from the enhanced 3270UI.
  • Using the Tivoli Data Warehouse is optional for the IBM Z® OMEGAMON AI for Db2 monitoring agent. The agent offers other long-term storage options.
  • The z/OS® persistent data store data sets, where some of the historical data is stored on z/OS, should have been configured earlier during Step 4.

Information sources: