IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Manage historical data > Use your historical data for analytic usage

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Examples of historical data collection for analytics

Examples of historical data collection to CSV files and to the Tivoli Data Warehouse are provided for your reference. In the examples included in this topic, the Warehouse Proxy agent is installed on a UNIX computer. If your Warehouse Proxy agent is installed on a Windows computer, edit the KHDENV file.


Private history data is collected every 10 minutes and sent to a CSV file every 60 minutes

Warehouse Proxy agent configuration

In the file hd.ini set:

  • KHD_CSV_OUTPUT_ACTIVATE=Y

  • KHD_CSV_OUTPUT=/wpatest2

Private situation configuration

In the file <ITMHOME>/localconfig/lz/lz_situations.xml set: 

    <PRIVATECONFIGURATION>
<HISTORY Table="Linux_Disk" Interval="10" Export="60" USE="A">
    </HISTORY>
</PRIVATECONFIGURATION>

Result

LNXDSK* files are written to the /wpatest2 folder every 60 minutes.


Private history data is collected and sent to the CSV file every 1 minute

Warehouse Proxy agent configuration

In the file hd.ini set:

  • KHD_CSV_OUTPUT_ACTIVATE=Y

  • KHD_CSV_OUTPUT=/wpatest2

Private situation configuration

In the file <ITMHOME>/localconfig/lz/lz_situations.xml set: 

    <PRIVATECONFIGURATION>
<HISTORY Table="Linux_Disk" Interval="1" Export="1" USE="A">
    </HISTORY>
<HISTORY Table="Linux_CPU" Interval="1" Export="1" USE="A">
    </HISTORY>
<HISTORY Table="KLZ_CPU" Interval="1" Export="1" USE="A">
    </HISTORY>
<HISTORY Table="Linux_Process" Interval="1" Export="1" USE="A">
    </HISTORY>
</PRIVATECONFIGURATION>

Result

LNXDSK* , LNXPROC*, LNXCPU*, and KLZCPU* are written to the /wpatest2 folder every 1 minute.


Private history data is sent to the Tivoli Data Warehouse and some data is sent to the CSV file

Warehouse Proxy agent configuration

In the file hd.ini set:

  • KHD_CSV_OUTPUT_ACTIVATE=Y

  • KHD_CSV_OUTPUT=/wpatest2

  • KHD_CSV_OUTPUT_TAGGED_ONLY=N

  • KHD_CSV_OUTPUT_LIST=LNXPROC

Private situation configuration

In the file <ITMHOME>/localconfig/lz/lz_situations.xml set: 

    <PRIVATECONFIGURATION>
<HISTORY Table="Linux_Disk" Interval="1" Export="15">
    </HISTORY>
<HISTORY Table="Linux_CPU" Interval="1" Export="15" >  
  </HISTORY>
<HISTORY Table="KLZ_CPU" Interval="1" Export="15">  
  </HISTORY>
<HISTORY Table="Linux_Process" Interval="1" Export="15">  
  </HISTORY>
<HISTORY Table="KLZ_Disk" Interval="1" Export="15" >  
  </HISTORY>
</PRIVATECONFIGURATION>

Result

LNXPROC* files are written to the /wpatest2 folder. (If you are using private history collection with the USE="A" parameter, more data is produced.) 

    ls -latr /wpatest2
total 2148
drwxr-xr-x  52 root root 2048 Nov 14 08:40 ..
-rw-r--r--   1 root root 379967 Nov 15 11:41 
    LNXPROC_1111115113805000_1111115114405072_00000.csv
-rw-r--r--   1 root root 381393 Nov 15 11:41 
    LNXPROC_1111115114405073_1111115115005142_00001.csv
-rw-r--r--   1 root root 123331 Nov 15 11:42 
    LNXPROC_1111115115005143_1111115115205154_00002.csv
drwxr-xr-x   2 root root 160256 Nov 15 11:42 .

All historical collections data is inserted into the Tivoli Data Warehouse.


Private history data is sent to only the Tivoli Data Warehouse

Warehouse Proxy agent configuration

In the file hd.ini set:

  • KHD_CSV_OUTPUT_ACTIVATE=N

Private situation configuration

In the file <ITMHOME>/localconfig/lz/lz_situations.xml set: 

    <PRIVATECONFIGURATION>
<HISTORY Table="Linux_Disk" Interval="1" Export="15">
  </HISTORY>
<HISTORY Table="Linux_CPU" Interval="1" Export="15" >
  </HISTORY>
<HISTORY Table="KLZ_CPU" Interval="1" Export="15">
  </HISTORY>
<HISTORY Table="Linux_Process" Interval="1" Export="15">
  </HISTORY>
<HISTORY Table="KLZ_Disk" Interval="1" Export="15" >
  </HISTORY>
</PRIVATECONFIGURATION>

Result

Data is sent only to the Tivoli Data Warehouse.


Private history data is sent only to the Tivoli Data Warehouse for one agent, and sent only to the CSV file for another agent

Warehouse Proxy agent configuration

In the file hd.ini set:

  • KHD_CSV_OUTPUT_ACTIVATE=Y

  • KHD_CSV_OUTPUT_TAGGED_ONLY=Y

Private situation configuration on an agent running on HOST1

In the file <ITMHOME>/localconfig/lz/lz_situations.xml set: 

    <PRIVATECONFIGURATION>
<HISTORY Table="Linux_Disk" Interval="1" Export="15">
  </HISTORY>
<HISTORY Table="Linux_CPU" Interval="1" Export="15" >
  </HISTORY>
<HISTORY Table="KLZ_CPU" Interval="1" Export="15">
  </HISTORY>
<HISTORY Table="Linux_Process" Interval="1" Export="15">
    </HISTORY>
<HISTORY Table="KLZ_Disk" Interval="1" Export="15" >
  </HISTORY>
</PRIVATECONFIGURATION>

Private situation configuration on an agent running on HOST2

In the file <ITMHOME>/localconfig/lz/lz_situations.xml set: 

    <PRIVATECONFIGURATION>
<HISTORY Table="Linux_Disk" Interval="1" Export="1" USE="A">
  </HISTORY>
</PRIVATECONFIGURATION>

Result

Data of agent on HOST1 is sent to the Tivoli Data Warehouse.

Data of agent on HOST2 is sent to the CSV file. 

    -rw-r--r--   1 root root 1570 Nov 16 08:48 
    LNXDISK_1111116085832000_1111116085832007_00017.csv
-rw-r--r--   1 root root 1570 Nov 16 08:49 
    LNXDISK_1111116085932000_1111116085932007_00018.csv
-rw-r--r--   1 root root 1570 Nov 16 08:50 
    LNXDISK_1111116090032000_1111116090032007_00019.csv


Enterprise history data is sent to the CSV file and the Tivoli Data Warehouse

Warehouse Proxy agent configuration

In the file hd.ini set:

  • KHD_CSV_OUTPUT_ACTIVATE=Y

  • KHD_CSV_OUTPUT=/wpatest2

  • KHD_CSV_OUTPUT_TAGGED_ONLY=N

The default value for the KHD_CSV_OUTPUT_TAGGED_ONLY variable is Y. If this variable is set to Y, data is written to the CSV files only when data is tagged in private history.

Enterprise historical collection configuration

Create the Historical Enterprise Collection in the Tivoli Enterprise Portal GUI.

Note: You do not need to edit the lz_situations.xml file.

Result

The CSV files related to the enterprise collection set on the Tivoli Enterprise Portal GUI are created in the /wpatest2 folder. Data is also sent to the Tivoli Data Warehouse.

Note: If the user also has private history by USE="A", these files are also sent to the CSV file and the Tivoli Data Warehouse.


Enterprise history data is sent only to the Tivoli Data Warehouse

Warehouse Proxy agent configuration

Complete one of the following options:

  • Do not set any KHD_CSV_* variables in the hd.ini file.

  • OR

  • In the hd.ini file, ensure the KHD_CSV_OUTPUT_TAGGED_ONLY variable is set to the default value of Y.

Enterprise historical collection configuration

Create the Historical Enterprise Collection in the Tivoli Enterprise Portal GUI.

Note: You do not need to edit the lz_situations.xml file.

Result

Collection data is sent only to the Tivoli Data Warehouse.


Parent topic:

Use your historical data for analytic usage

+

Search Tips   |   Advanced Search