Traffic Page
The Monitor Traffic page displays request traffic traveling between TDV clients, TDV servers, and underlying data sources.
With default settings and monitoring a single TDV instance, the Traffic display will look similar to this.
A TDV client is a an aggregate of TDV sessions that have the same host, client type, user name, and domain name. This allows similar sessions from TDV nodes in a cluster or connectionless sessions, such as those created by Web services, to appear as one logical TDV client for monitoring purposes.
A TDV client appears when at least one TDV session exists on any TDV node in the cluster for a given set of host, client type, user name, and domain name. When all such TDV sessions are closed, the TDV client becomes idle and is displayed as disabled. If the TDV client is idle for longer than the Idle Client Timeout configuration parameter setting, it is removed the next time the Monitor Server purges expired clients. The timing of the purge is controlled by the Expired Client Purge Period configuration parameter setting.
Activity balls display client requests for data and data returning from data sources. For small numbers of requests, the number of activity balls represents the number of requests. If tens of requests are being made along a particular track, a second column of balls appear within the track. If hundreds of requests are being made, a third column appears, and so on.
The activity balls are color-coded: client requests or data source accesses are light blue; activity balls for completed requests move from the TDV server to the clients, green for successful, yellow for terminated, and red for failed.
In the example above, the activity balls illustrate Studio requesting data from a view that is based on two data sources.
The following example shows the Monitor’s Traffic display of a four-node cluster.
For more information about the Traffic page, see these sections:
