APM Server version:
APM Agent language and version:
<TargetFramework>net5.0</TargetFramework> <PackageReference Include="Elastic.Apm.NetCoreAll" Version="1.11.0" />
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
Elk stack installed from Helm charts (K8S in AKS)
Fresh install or upgraded from other version?
Is there anything special in your setup?
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
Steps to reproduce:
- I note systematic differences in response time between APM and external clients such as Postman, on the following example, Postman reports 183ms while APM tells 76ms, who is right and how can we explain the difference ?
Is it about json payload download that is not computed in APM (the payload in my API is about 19.5KB) ?
Here are some typical response time (in ms)
APM | Postman
76 | 183
108 | 211
75 | 231
73 | 160
82 | 103
- Second point is about the whole response time exposed in APM, it doesn't fit on the sum list of all actions involved, as for example the trigger of the following route (controller) tells 82ms, but when I'm summing the displayed response time of inner spans, I get 63,1ms and the top bar seems to show extra time, what is about ?
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):