Could you tell me what is the server/network/idle/other time for SSL?
And what does each time mean?
According to the document, the server/network/idle/other time is based on the time of each HTTP hit. https://www.dynatrace.com/support/doc/dcrum/refer...
In the case of SSL, DCRUM cannot measure the time of each hit.
I think it is not possible to measure the server/network/idle/other time.
But the time breakdown appears in the Operation Explorer.
The new architecture of AMD does not include the time spent on TCP and SSL session establishment in the overall operation time because modern browsers pre-connect to the network automatically without any actions performed by the user. The browser simply starts the session when it is opened. If the user remains inactive for a longer period of time, taking into account the initial session establishment would artificially prolong the calculated operation time.
Due to above changes, operation time, network time, and its component request time may present lower values.
The same information you can find in the following link.
Thank you for your response.
What I want to know is what is the server/network/idle/other time in SSL operation.
In our environment, the server and the network time of "Encrypted data exchange" and "SSL connection Hello" have appeared. How is the server/network/idle/other time of these operations calculate in case of SSL?
I would like to confirm whether the breakdown can be used for something like isolating problems.
You can absolutely use the operation breakdown to isolate the situation because one of the purpose of DCRUM is FDI.
As mentioned in the first comments that AMD does not include the time spent on TCP and SSL session establishment in the overall operation time.
Have a look on the below link for the monitoring of secure traffic.
Full SSL handshake has two multi-packet hits, on top of the TCP handshake. So there's a lot of sense in measuring SSL connection setup delay as a multi-hit operation, and DC RUM does exactly that. You will see whether it's the server who delays the client's request for connection (server time) or whether it's the client who lags confirming the connection specification (will surface as idle time), or whether it's the network that takes long to transmit (not small) SSL handshake messages (network time). You may have a look into the https://university.dynatrace.com/elearning/dcrum/519/21878 webinar, SSL handshake is discusses there in a bit more details.