Include the Liberty dispatch time within z/OS Connect SMF and monitor data (e.g. Omeagamon for JVM and OEM vendors just as Dynatrace)

Without the Liberty Dispatch time we have had instances of large amounts of time in our API call chain being unaccounted for. We had a recent incident with IBM (TS010301362) to assist in identifying what appeared to be a random 5 second spike in response time that happened multiple times per day. z/OS Connect and Omegamon data showed z/OS Connect response time <20 ms, so the problem was believed to be elsewhere. With a detailed investigation of the path, evidence continued to point at the Mainframe causing the delay. A sniffer trace confirmed that the Mainframe acknowledged the payload and then took 5 seconds to respond. Initial contact with IBM Comm Server support was that the ACK was because the application received the payload. Z/OS Connect support reported the payload was not received until 5 seconds later. With further escalation the incident was routed to Liberty support who assisted in finding the 5 second delay from Liberty receiving the payload to sending it to z/OS Connect. This required a Javacore trigger for 4 second delays and access logging defined with logFormat='%h %u %t "%r" %s %b %D %{R}W %{remote}p %p' />. IBM was able to localize the problem with the javacore dump and the access log showed us the 5 seconds via the %D (elapsed time of the request - millisecond accuracy, microsecond precision). The javacore trigger and access log do not appear to be settings we want to keep active in our production environment and neither provides visibility through any monitoring tools. It is very important that all time for the z/OS Connect API, and the underlying middleware, on the mainframe is available and reported via monitors so we don't have unaccounted for time. The lack of visibility inhibits problem determination and erodes confidence in z/OS Connect as a viable solution. This continues to be a problem for us as people report "back-end slowdowns" that can't be easily visualized or investigated. The Liberty time is reported in SMF120 records: SM120BBW Request Start Timestamp - GMT timestamp, in STCK format, when the request started dispatch SM120BBX Request End Timestamp - GMT timestamp, in STCK format, when the request ended dispatch but the liberty layer is not customer managed and it's data is not exposed as part of z/OS Connect even though it packaged as part of it.