Information about accessing CEM data (not aggregated) and on how long it is retained after capture.

Document ID : KB000047957
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Three types of raw APM CE (CE) data (Defects, Stats and BtStats) may be accessed via the APM CE (CEM) UI and extracted for reports based on specific data retention rules for each data type.

Solution:

There are 3 types of APM CE (CEM) data: Defects, Stats and BtStats

  • Defects
    After processing the transaction packets, the Tim generates defects in memory and every 5 seconds it writes out any defects from memory to a file. The files are then polled by the EM running the TIM Collection Service (TESS) and by default is stored in the APM database for 7 days. The number of days retained may be changed by the user via the “Delete Defects after” field under "Setup -> Incident Settings".
    It can be accessed via the UI using the Incident Management tab and it may be extracted using the Export Data tab or the Export Tool.
    After 7 days only hourly aggregated data or higher is available.
  • Stats
    Raw stats data is generated every hour and is stored in the APM database for 3 days (not user configurable).
    It can be accessed via the UI using the various Reports or Analysis Graphs tabs and it may be extracted using the Export Data tab or the Export Tool.
    After 3 days only daily aggregated data or higher is available.
  • BtStats
    BtStats data is generated every 15 seconds when the RTTM Collection Service is started under Tim Collection Services.
    It is not stored in the APM database but is stored in the Collector SmartStor and is therefore subject to the usual user-defined SmartStor tier age rules.
    It can be accessed via the UI using the Workstation Investigator where it is located under the "<Collector>|CEM|TESS Agent" node
    Like any other SmartStor data, it may be extracted using the Introscope JDBC API tool.

For additional information on maintaining good APM Database performance please see this Community document: Database Maintenance