Kibana version :
7.4.0 [Cloud]
Elasticsearch version :
7.4.0 [Cloud]
APM Server version :
7.4.0
APM Agent language and version :
dotnet 1.2
Browser version :
N/A
Original install method (e.g. download page, yum, deb, from source, etc.) and version :
7.0.0 -> 7.2.0 -> 7.4.0 through deb
Fresh install or upgraded from other version?
7.0.0 -> 7.2.0 -> 7.4.0 through deb
Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
NGINX reverse proxy in front of APM Server and between APM Server and Logstash server
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant) :
We have an issue with our APM dotnet agents (1.2) which intermittently shows transfer failures of a specific transaction. Most of them are transferred fine but about 10% is failing. The mentioned TraceIds are not found in the APM indexes.
{PayloadSenderV2} Failed sending events. Following events were not transferred successfully to the server (https://xxxx/):
Elastic.Apm.Metrics.MetricSet,
Transaction{Id: 334a2fe2352bf342, TraceId: 5367449ab20145e9bc8074ef2d784b47, ParentId: null, Name: GET Preference/HealthCheck, Type: request, IsSampled: True},
Elastic.Apm.Metrics.MetricSet,
Elastic.Apm.Metrics.MetricSet,
Transaction{Id: 1b2f3a30bc4fa415, TraceId: f0218af56d117708ffcf30e1dd932a5e, ParentId: null, Name: GET Preference/HealthCheck, Type: request, IsSampled: True},
Elastic.Apm.Metrics.MetricSet,
Transaction{Id: 7900165db05c20bb, TraceId: fee7c606f1c28503c32fa991774f7cab, ParentId: null, Name: GET Preference/HealthCheck, Type: request, IsSampled: True},
Elastic.Apm.Metrics.MetricSet
Is an empty ParentId an issue? Where should investigate to find out under what circumstances the transfer fails?