Normally during an agent connect process we have the last phase Agent Reporting, at the end of service resolution agent data is reported back to the Configuration Server as QMSG calls. This object is one of the many that get sent to up at this phase.

SAPSTATS is generated on clients using Client Operation Profiles, and is used to report the Server Access Profile (SAP) status and usage statistics from the Radia Client. The SAPSTATS object contains all the variables defined in the SAP class (like PRIORITY, URI, ROLE, BANDWIDTH) along with the some more usage statistics related variables listed below.

BYTERCVD Bytes received
BYTESENT Bytes sent
ERRCOUNT Number of errors
FILEMISS Number of files not found
FILERCVD Number of files received
FILESENT Number of files sent
SPEED Speed to the SAP from the client computer measured in Bytes per second
STATUS Status of this SAP
(000= SAP was accessed successfully
920 = SAP could not be accessed
999 = SAP was not used)

Can this best be used to give more visibility to the health of the environment?

In Radia 9.x SAPSTAT processing is available but turned off by default. You can enable SAPSTATS processing in the CLIENT.Core Settings.SAPSTATS Y. The RIM table is sapstats.

In older versions of Radia you need to create the .sql file for the table and map it in the taskend.tcl file. I built custom reports to show SAPSTAT data for 5.x/7.x along with the sql file and taskend.tcl mapping.