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

decode error when sending span.context.destination.port as string #1885

Open
kruskall opened this issue Aug 3, 2023 · 1 comment
Open

decode error when sending span.context.destination.port as string #1885

kruskall opened this issue Aug 3, 2023 · 1 comment

Comments

@kruskall
Copy link
Member

kruskall commented Aug 3, 2023

Describe the bug:

According to the specification, span.context.destination.port must be a number.

As part of the ops KPI review we've been investigating the following errors in ecs logs:

decode error: data read error: v2.spanRoot.Span: v2.span.Context: v2.spanContext.Destination: v2.spanContextDestination.Port: readUint64: unexpected character: �, error found in #10 byte of ...| "port": "9243", "se|..., bigger context ...|redacted", "port": "9243", "service": {"resource": "elasticsearch/aaaa|...
decode error: data read error: v2.spanRoot.Span: v2.span.Context: v2.spanContext.Destination: v2.spanContextDestination.Port: readUint64: unexpected character: �, error found in #10 byte of ...| "port": "9|..., bigger context ...|: "redacted", "port": "9|...

"port": "9243" is not valid format and the apm-server will fail to ingest those transactions.

To Reproduce

I don't have steps to reproduce, this is part of the ops KPI review and was observed in the ecs logs.

Environment (please complete the following information)

Most of the errors are coming from the following user agent: apm-agent-python/6.18.0

This happens on multiple apm-server versions. Both 7.x and 8.x, including the latest 8.9.0.

Additional context

none

@basepi
Copy link
Contributor

basepi commented Aug 8, 2023

Thanks for the report, we'll investigate.

@basepi basepi added this to the 8.11 milestone Aug 23, 2023
@basepi basepi removed this from the 8.11 milestone Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Planned
Development

No branches or pull requests

2 participants