Dec 10, 2016 at 09:47 AM ·
Feb 20 at 08:53 AM
kdata - Provides distributions defined on the AMD/RUM Console and reported on the CAS - you can call it buckets: how many Operations had time 0-3 sec, how many 3-5sec and how many 5-8sec. Used only by CAS < 12.4.
jdata - These files keeps th current state of autolearning mechanism on the AMD - which URLs are already in the space of members, and which are still candidates. It's used to recover this information after RTM/AMD restart. Used only by the AMD.
zdata - Contains records for entire traffic that is set to be monitored: all client-server conversation seen during last 5 minutes with accompanied URLs and usernames (if applicable) plus all the metrics. Used only by CAS. Rpoduced by two processes on the AMD: RTM and NFC is flows from routers are enabled.
vdata - Contains all the hits (not URLs) of the operations that are set to be monitored and reported on ADS. The most detailed set of traffic information we keep. Used only on ADS. Base on scalability mode can be either read by ADS or kept on AMD and being queried by ADS.
hpdata, cpdata - Base on configuration, some of the hits from vdata can be composed into operations. Hpdata contains operations for HTTP-based anlyzers, cpdata contains the rest of non-HTTP operations (operations for DB, OF, MQ, etc).
transdata - AMD can produce Sequence Transactions kept by transdata, these files can be produced also by other products like Enterprise Synthetic Monitoring or Gomez. Used both by CAS and ADS.
g) Vdata_idx - an index file for quick look ups of records in corresponding vdata file. Used by AMD if ADS does not process vdatas in Large mode.
amdstatsdata - provides wide range of statistics available on "AMD Statistics" reprot on the CAS < 12.4
amddata - same as above but for CAS >= 12.4
gatestatsdata - component of amdstatsdata.
headerdata - if enabled contains full HTTP headers, used by ADS. Related hpdata and vdata are required to go from particular URL to its header.
idata - If RUM Console -> Global -> database Monitoring -> Global -> Log SQL statements is turned on then first 1024 bytes of full DB queries (not normalized) are logged to these files, which are not read or needed by any report server. They can be used for manual and custom processing.
ctxdata - contains Citrix performance data like CPU/memory/disk usage, etc,
ndata - Layer 2 data available in CAS: VLAN, QoS, etc