eG Monitoring
 

Measures reported by AtcCallsTest

This test reports statistics pertaining to the authentication service of the Voyager. The authentication service, which exists within each Transaction Processor, provides a central user authentication source for a number of Voyager products and add-ons, including consumer and business banking, bill payment, and One Source Register (OSR). The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Database_calls_rate The rate of direct database calls during the last minute Calls/Sec A decrease in the value of this measure would indicate that there is a significant slowing of the Authentication Service and it cannot keep up with the load required.
HostServer_queue_size The length of a queue of transactions awaiting assigment to a host server Number Ideally, the queue size should be low.
HostServer_response_rate The rate of responses from the host server during the past minute Reqs/Min  
Pending_auth_calls The count of authentication API calls currently in progress Number A large increase in the value of this measure points towards a degraded response time between the Transaction Processor and the host, or a slowdown in the host itself.
Pending_db_calls The count of database API calls currently in progress Number A large increase in the value of this measure points towards a degraded response time between the Transaction Processor and the TP database.
Pending_ident_calls The count of identity API calls currently in progress Number  
Pending_pv_calls The count of pin vault API calls currently in progress Number  
Pinvault_calls_rate The rate of pin vault calls. The Pin Vault is where encrypted aliases are stored and the data is stored with the rest of the authorization and authentication database, but is managed by a distinct COM (in-proc) object. Secs  
Token_cache_ratio The token cache ratio during the last minute Percent  
Valid_auth_tokens The count of valid authentication tokens. A token is a 32-character string that is a hex representation of a 128-bit random number. A token is created by combining a GUID with other environmental data; this information is then sent through an MD5 secure hash Number A sharp increase in this measure may mean sessions are not expiring, there are too many users on the system, and response times are high. If this measure continues to increase even after peak load, make sure that the AuthTokenPurge Task in SQL Server is running regularly.