We only see ACK RTT on "All Others" operations.
We see correctly standard RTT on all operations.
We checked the option "Monitoring Persistent Session" into the Software Service configuration.
For your point of view, what would be the reason not to calculate this metric (ack rtt) on all operations?
It is the same for all Software Services.
In the example below (DMI into Partner Portal 12.4) the result is the same.
For a specific software service, ACKs RTT are calculated only for all others operations.
Can you please check the below options in the CAS >> Tools >> Diagnostics >> Console >> Advanced Properties Editor?
By default, the metrics used for determining the network performance in CAS reports are: average end-to-end RTT, average upstream loss rate, and average downstream loss rate. The ACK RTT metric is not taken into account for this calculation.
In some situations, however, end-to-end RTT may prove insufficient and you may need to add ACK RTT as a performance criterion. This may be due to long session duration, when the frequency of RTT measurements is rather low.
To include client ACK RTT in the measurement algorithm, set the
LOC_USE_CLI_ACK_RTT_THproperty value to
Please see the below document link.
Did you double check the remaining settings in the link document? If YES !!!
Then I would recommended to open a case with the DynaTrace Support to understand the limitations of ACK measurements.