Create historical data collections

TIP

To ensure that ODP forwards attributes to Instana as soon as you start collecting them, update the ODP collection configuration member KAYOPEN before creating the corresponding historical data collections.

WARNING

With higher granularity (a smaller interval means more data collected) there are 2 obvious considerations:

  1. CPU overhead on data collection and retrieval;
  2. DASD space to hold historical tables.

Should you grow in CPU usage or Persistent Data Store, consider raising the interval and/or skipping warehousing for certain tables on PDS and just go with open data.

Create the following historical data collections for the JVM agent. This can be done via the E3270UI or the Tivoli Enterprise Portal within the JVM workspace.

table_name field valueAttribute groupCollection interval (minutes)
addrmemJVM Address Space5
gcsummJVM Garbage Collection5
healthJVM Health Summary5
natmemJVM Native Memory5
zcsummJVM zOSConnect Summary5
zosmemJVM Virtual Memory5
wlpsesmJVM_Liberty_Sessions1
envdetJVM_Environment_Data_Details15
wlpwbamJVM_Liberty_Web Applications1
wlpthplmJVM_Liberty_Thread_Pool1
wlpcnplsJVM_Liberty_Connection_Pool1
wlpsrvinJVM_Liberty_Server_Info1
environJVM_Environment_Data15
zcoutbsumJVM_zOSConnect_APIRequester_Summary5
Last Updated:
Contributors: Jim Porell