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.
Group | Summarization | Pruning |
---|---|---|
Aggregate Context |
|
|
Aggregate Count Metrics |
|
|
Aggregate Gauge Metrics |
|
|
Aggregate Interactions |
|
|
Interaction Count Metrics |
|
|
Interaction Gauge Metrics |
|
|
Metric Types |
|
|
Metric Units |
|
|
String Map |
|
|
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.
Group | Summarization | Pruning |
---|---|---|
Aggregate Interactions |
|
|
Aggregates |
|
|
Interactions |
|
|
Transaction_Instance_ |
not required |
|
Transaction_Instance_ |
not required |
|
Transaction_Instance |
not required |
|
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.