In both cases Tivoli Enterprise Monitoring Agent and Tivoli Enterprise

In both cases tivoli enterprise monitoring agent and

This preview shows page 194 - 196 out of 232 pages.

In both cases (Tivoli Enterprise Monitoring Agent and Tivoli Enterprise Monitoring Server), the binary data is considered short-term because it is only designed for 24-hour access. When the Summarization and Pruning Agent is configured, it can be set up to prune this short-term data. After the short-term data is successfully loaded into the Tivoli Data Warehouse V2.1 to the Warehouse Proxy Agent, it is pruned on Tivoli Enterprise Monitoring Agent or Tivoli Enterprise Monitoring Server if it is older than 24 hours. If the Warehouse Proxy Agent is not configured to collect the short-term data, a user-defined pruning job will have to be implemented. Long-term data Long-term data in IBM Tivoli Monitoring V6.1 is typically referred to as data that is older than 24 hours and has been collected up to the Tivoli Data Warehouse V2.1 RDBMS to the Warehouse Proxy Agent. The long-term data resides in tables in the Tivoli Data Warehouse V2.1 database. The long-term RDBMS tables contain detailed data and summarized data in Tivoli Data Warehouse V2.1. The Summarization and Pruning Agent can be configured to run every day to roll up data from the detailed level to hourly, weekly, monthly, quarterly, and yearly. The Summarization and Pruning Agent also prunes the summarized tables. 7.4.2 Data collection options To provide flexibility in using historical data collection, Tivoli Enterprise Portal permits you to: Turn history collection on, or turn off all history collection for multiple selected Tivoli Enterprise Monitoring Servers and multiple selected attribute groups for a product. Save the history file at the Tivoli Enterprise Monitoring Server or at the remote agent. Define the collection interval used to save data into the Tivoli Data Warehouse. It can be every hour or once a day or off. Define how you want to summarize your historical data. Define how and when you want to prune your historical and detailed data. Historical data collection can be specified for individual monitoring servers, products, and tables. However, all agents of the same type that report directly to the same Tivoli Enterprise Monitoring Server must have the same history collection options. In addition, for a given history table, the same history
Image of page 194
Chapter 7. Administration 179 collection options are applied to all monitoring servers for which that history table’s collection is currently enabled. History collection at the agent We normally recommend collecting history data at the agents. This provides the following benefits: Reduces agent to Tivoli Enterprise Monitoring Server network traffic because history data is not sent to Tivoli Enterprise Monitoring Server. Decreases Tivoli Enterprise Monitoring Server workload, especially when doing warehousing. Reduces history data file size because data for only that agent or node exists in the file. This is critical when warehousing is enabled.
Image of page 195
Image of page 196

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture