otelmap: handle conversion of struct types#45234
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error. To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values.
|
@Mergifyio backport 9.0 9.1 |
✅ Backports have been createdDetails
|
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error. To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values. (cherry picked from commit 2685f9c)
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error. To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values. (cherry picked from commit 2685f9c)
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error. To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values. (cherry picked from commit 2685f9c)
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error. To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values. (cherry picked from commit 2685f9c) Co-authored-by: Mauri de Souza Meneguzzo <mauri870@gmail.com>
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error. To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values. (cherry picked from commit 2685f9c) Co-authored-by: Mauri de Souza Meneguzzo <mauri870@gmail.com>
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error. To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values. (cherry picked from commit 2685f9c) Co-authored-by: Mauri de Souza Meneguzzo <mauri870@gmail.com>
Should we have an issue tracking this? |
More likely, yes. I want to confirm if it is feasible first. When I did a first take on this I found lots of little discrepancies between the current otelmap and the libbeat generic serializer. If we are bound to change libbeat serializer to get the same behavior then it's not worth it, as we risk breaking standalone beats. |
Proposed commit message
The otelmap package does not handle struct types properly, the convertion of a struct results in a string error.
To follow the libbeat behavior, handle struct types the same way, by serializing to json and back, resulting in a map of keys and values.
We have plans to try and extend otelmap to use the libbeat generic serializer, but that is part of a large refactor that should be done in a separate PR.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
structtypes #45005