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
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
Each TUST packet contains an standard header used to define who generated the information and whom it is intended for
|f100||Type||Type of report.
|f105||InstanceId||Unique instance id. A process will use the same value for each packet, but a new value may be allocated for later runs.|
|f110||ComputerName||Name of computer|
|f120||LocalIP||Users local IP address|
|f121||1. Indicates this is a remote monitoring report|
|f122||SampleDt||Current Date/Time (localtime)|
|f123||NextDt||Expected time of next report. Clients will typically report less frequently over idle periods such as during the night.|
|f124||SubType||Additional type information. Used for some types that may send different information packets|
Periodic Monitoring Report
This packet is sent from applications performing periodic monitoring of system performance.
|f200||Free space on current working drive. Reporting in MB|
|f201||CPU used by this process since start.|
|f202||CPU used by this process since start.|
|f203||CpuLoad||Current system wide CPU load percentage|
|f204||MemLoad||Current system wide memory load percentage|
|f205||Small random IO performance results. Array of "short" with most recent sample first. Reported as whole millisecond values. -1 indicates sample failure|
|f768||Constant 2 for periodic report|