IBM Tivoli Composite Application Manager for Transactions, Version 7.4.0.0

Setting up historical data collection for Transaction Tracking

In order to view data in the history workspaces, you first need to configure historical data collection for the Transaction Reporter.

History data collection includes summarization and pruning settings for data that is stored in the Tivoli Data Warehouse. Specify history data collection through the History Collection Configuration feature in the Tivoli Enterprise Portal. (You must have Configure History permission to see and use this feature.)

Important: If you want to use historical data for both agentless and agent-based workspaces, ensure that all tables described in Table 1 and Table 2 are added to the warehouse.

See the IBM Tivoli Monitoring User's Guide for detailed information about history data collection.

Table 1 gives suggested values for the fields in the History Collection Configuration window for the new workspaces introduced in Transaction Tracking V7.3. These workspaces mainly present agentless data.
Table 1. Suggested history collection configuration settings for Transaction Tracking V7.3 (agentless) workspaces
Group Summarization Pruning
Aggregate Context
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Aggregate Count Metrics
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Aggregate Gauge Metrics
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Aggregate Interactions
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Interaction Count Metrics
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Interaction Gauge Metrics
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Metric Types
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Metric Units
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
String Map
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 7 days
  • Hourly keep 7 days
  • Detailed data keep 7 days
Table 2 gives suggested values for the fields in the History Collection Configuration window for the older workspaces in Transaction Tracking. These workspaces mainly present agent-based data.
Table 2. Suggested history collection configuration settings for Transaction Tracking V7.2.0.2 and earlier (agent-based) workspaces
Group Summarization Pruning
Aggregate Interactions
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 14 days
  • Hourly keep 7 days
  • Detailed data keep 3 days
Aggregates
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 14 days
  • Hourly keep 7 days
  • Detailed data keep 3 days
Interactions
  • Weekly
  • Daily
  • Hourly
  • Weekly keep 2 months
  • Daily keep 14 days
  • Hourly keep 7 days
  • Detailed data keep 3 days

Transaction_Instance_
Context

not required
  • Detailed data keep 30 days

Transaction_Instance_
Interactions

not required
  • Detailed data keep 30 days

Transaction_Instance
Instances

not required
  • Detailed data keep 30 days
Tip: Setting warehouse values for Transaction_Instance tables does not add instance data to the warehouse. Ensure the situations Failed_Transactions and Slow_Transactions that send instance data to the warehouse are also enabled.


Last updated: September 2014