IBM Tivoli Monitoring, Version 6.3

Disable logging to the WAREHOUSELOG table and use trace to monitor Warehouse Proxy Agent export activity

During normal processing, the WAREHOUSELOG table is appended each time an agent successfully exports a batch of attribute group rows to the warehouse database. The entries in the WAREHOUSELOG table record the agent name, attribute group name, number of rows exported, the Warehouse Proxy Agent involved, and the time of the export.

For large environments, the WAREHOUSELOG table can grow very large, and managing the table can add unnecessary overhead for the Summarization and Pruning Agent. A more efficient approach for monitoring Warehouse Proxy Agent export activity is to disable logging to the WAREHOUSELOG table, and instead turn on a trace setting that records similar information to the Warehouse Proxy Agent trace log.

Note: Warehouse Proxy Agent logging to the WAREHOUSELOG table is disabled by default. The self-monitoring workspaces provided by the Warehouse Proxy Agent provide sufficient information to determine if the agent is operating correctly.

To disable logging to the WAREHOUSELOG table manually, add the following to the Warehouse Proxy Agent configuration file:

KHD_WHLOG_ENABLE=N

To turn on tracing for Warehouse Proxy Agent export activity, set the trace options on the KBB_RAS1 entry in the Warehouse Proxy Agent configuration file:

KBB_RAS1=ERROR (UNIT:khdxdbex OUTPUT)

This trace setting writes an entry to the trace log every time an agent exports a batch of attribute group rows to the warehouse database. The trace entry contains similar information to the information that is written to the WAREHOUSELOG, that is agent name, attribute group name, and number of rows.

You can tail the Warehouse Proxy Agent trace log to monitor Warehouse Proxy Agent export activity in real-time.

Example:
# tail -20f prfr1s33_hd_4c582197-02.log
(4C5DC26D.00EA-14:khdxdbex.cpp,3022,"endProcessSample") Inserted 4 rows of data into
"Linux_VM_Stats" (LNXVM appl KLZ) for "177:prfr2s34:LZ" , status 0
(4C5DC26D.00EB-BD:khdxdbex.cpp,3022,"endProcessSample") Inserted 4 rows of data into
"Linux_VM_Stats" (LNXVM appl KLZ) for "228:prfr2s34:LZ" , status 0
(4C5DC26D.00EC-16:khdxdbex.cpp,3022,"endProcessSample") Inserted 16 rows of data into
"Linux_Network" (LNXNET appl KLZ) for "125:prfr2s34:LZ" , status 0

The trace setting described in this section writes export information in the trace log, which does wrap and will not grow indefinitely.

Feedback