Add High Speed Connector metrics as a CDC data flow for RTMC

HSC end point metrics are maintained in the group control block (e.g. number of application timeouts), and socket control block structures (e.g. total number of APIs, Total number of errors etc). HSC end point metrics should be added to RTMC as a CDC data flow to allow for monitoring, alerting, trending, and trouble shooting.

At a minimum we think the following metrics should be provided in these feed :

• APIs per second per endpoint (based on change in cumulative count in scb_api_tot_ct) + total APIs per second for all endpoints in a group

• Errors per second per endpoint (based on chnage in cumulative count in scb_err_tot_ct) + total errors per second for all endpoints in a group

• Application timeouts per second (believe gcb_num_appl_timeout from the group control block is the correct metric)

• Avg response time (mics) per endpoint for the last minute and for all APISs (scb_cur_wdw_api_resp and scb_cur_api_resp)

• current number of active sessions (scb_asess)

• current number of sockets in use (scb_inuse)

• max number of sockets (scb_maxSocket)

• starting sockets (scb_startSocket)

• number of connects per second (from change in scb_num_connects)

• number of failed connects per second (from change in scb_num_connects_fail)

In addition, it would be useful to send error information on the last conn fail if a new conn failure occurs since the last send of data was done. Useful error information for the latest conn failure would include:

• Last conn fail API (scb_last_conn_error_api)

• Last conn fail port (scb_last_conn_error_port)

• Last conn fail SSL reason code (scb_last_conn_error_ssl_reason

• Last conn fail time (scb_last conn_error_tod)

• Last conn fail result (scb_last_conn_error_verify_result)

• Last conn fail SSL error (scb_last_conn_error_ssl)