You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{PayloadSenderV2} Failed sending event.
APM Server response: status code: "BadRequest", content:
decode error: data read error: v2.transactionRoot.Transaction: v2.transaction.DroppedSpanStats: []v2.transactionDroppedSpanStats: v2.transactionDroppedSpanStats.Duration: v2.transactionDroppedSpansDuration.Sum: v2.transactionDroppedSpansDurationSum.Us: assertInteger: can not decode float as int, error found in #10 byte of ...|{"us":1940.382199999|..., bigger context
APM Agent version
1.25.0
Environment
Windows Server 2019
.NET Core 7.0.13
ASP.NET CORE
Describe the bug
Following error occures randomly in log files:
{PayloadSenderV2} Failed sending event.
APM Server response: status code: "BadRequest", content:
decode error: data read error: v2.transactionRoot.Transaction: v2.transaction.DroppedSpanStats: []v2.transactionDroppedSpanStats: v2.transactionDroppedSpanStats.Duration: v2.transactionDroppedSpansDuration.Sum: v2.transactionDroppedSpansDurationSum.Us: assertInteger: can not decode float as int, error found in #10 byte of ...|{"us":1940.382199999|..., bigger context
To Reproduce
Steps to reproduce the behavior:
ElasticApm:CentralConfig = false
ElasticApm:LogLevel = "Error"
ElasticApm:OpenTelemetryBridgeEnabled = false
ElasticApm:CloudProvider = "none"
ElasticApm:CaptureHeaders = false
ElasticApm:CaptureBody = false
any page
random usage of page
exception in log
Hint:
as stated here:
https://www.elastic.co/guide/en/apm/guide/current/api-transaction.html
the field "Us" is defined as integer:
"us": {
"description": "Us represents the summation of the span duration.",
"type": [
"null",
"integer"
],
"minimum": 0
}
But in this file:
https://github.com/elastic/apm-agent-dotnet/blob/v1.25.0/src/Elastic.Apm/Model/DroppedSpanStats.cs
in line 72 we see type "double"
Might this be the problem?
The text was updated successfully, but these errors were encountered: