Fieldpine Logo Documentation Home  

TUST status messages are sent as periodic status messages. They are primarily used for monitoring and instrumentation.

For details about information sent after an event, see TUEV Event Blocks

Packet Structure

TUST blocks share a single schema, but individual events are free to populate only those fields that are relevant. Conceptually it is like using a single database table with hundreds/thousands of columns, where each row is an event

Standard Header

Each TUST packet contains an standard header used to define who generated the information and whom it is intended for

f100TypeType of report.
  • 17 - QeDebug Packet. Type of packet is stored in f124
  • 512 - Periodic Monitoring Report
  • 256 - Database Status Info
f105InstanceIdUnique instance id. A process will use the same value for each packet, but a new value may be allocated for later runs.
f106System location
f108Device Fingerprint
f109DbidDatabase Id
f110ComputerNameName of computer
f120LocalIPUsers local IP address
f1211. Indicates this is a remote monitoring report
f122SampleDtCurrent Date/Time (localtime)
f123NextDtExpected time of next report. Clients will typically report less frequently over idle periods such as during the night.
f124SubTypeAdditional type information. Used for some types that may send different information packets

Optional Fields


Periodic Monitoring Report

This packet is sent from applications performing periodic monitoring of system performance.

f200Free space on current working drive. Reporting in MB
f201CPU used by this process since start.
f202CPU used by this process since start.
f203CpuLoadCurrent system wide CPU load percentage
f204MemLoadCurrent system wide memory load percentage
f205Small random IO performance results. Array of "short" with most recent sample first. Reported as whole millisecond values. -1 indicates sample failure
f768Constant 2 for periodic report
f770Reporting Agent