Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] v2.transactionDroppedSpansDurationSum.Us: assertInteger: can not decode float as int #2209

Closed
gnulp opened this issue Oct 27, 2023 · 3 comments
Labels

Comments

@gnulp
Copy link

gnulp commented Oct 27, 2023

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:

  1. Use this config '...'
    ElasticApm:CentralConfig = false
    ElasticApm:LogLevel = "Error"
    ElasticApm:OpenTelemetryBridgeEnabled = false
    ElasticApm:CloudProvider = "none"
    ElasticApm:CaptureHeaders = false
    ElasticApm:CaptureBody = false
  2. Then call '....'
    any page
  3. Then do '....'
    random usage of page
  4. See error
    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?

@gnulp gnulp added the bug Something isn't working label Oct 27, 2023
@kolbeck
Copy link

kolbeck commented Oct 31, 2023

I see the same problem.

@muhmuhhum
Copy link

I also have this issue and opened an issue #2200 which references a issue in the agent-nodejs package which got already fixed

@stevejgordon
Copy link
Contributor

Dupe of #2200

@stevejgordon stevejgordon closed this as not planned Won't fix, can't repro, duplicate, stale Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants