-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/elasticsearch] Workaround TSDB array dimension limitation for metrics OTel mode #35009
Merged
andrzej-stencel
merged 11 commits into
open-telemetry:main
from
carsonip:workaround-metrics-tsdb-array-dimension
Sep 6, 2024
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
9bc841e
Workaround TSDB array dimension limitation for metrics OTel mode
carsonip 0dff271
Merge branch 'main' into workaround-metrics-tsdb-array-dimension
carsonip d758f01
Add comment
carsonip 7a2c140
Merge branch 'main' into workaround-metrics-tsdb-array-dimension
carsonip b2d1d3d
Add changelog
carsonip 0ed6cd9
Fix compile error
carsonip 270ccf9
Test otel metrics array value
carsonip faf60a1
Refactor
carsonip d08e12e
Add test for OTel logs and traces
carsonip b567108
Make linter happy
carsonip d3e405f
Add EnsureCapacity
carsonip File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This not only affects array values but also other complex attribute values, like
ValueTypeMap
. Not quite sure how to deal withValueTypeBytes
tbh. How do we serialize it normally? Is that compatible with a field type that supports dimensions?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
according to https://opentelemetry.io/docs/specs/otel/common/
I don't think ValueTypeMap and ValueTypeBytes fall into these valid value types.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How are we dealing with cases where we get invalid attribute values? Are we ignoring them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We had a similar issue in apm-server where otlp events with non-compliant attributes cause panics: elastic/apm-server#13703
In es exporter, by looking at the code, ValueTypeMap will be successfully encoded as objects, ValueTypeBytes will be ignored, non-homogeneous arrays will be successfully encoded. Ideally they should be dropped explicitly with a warning, but as these are non-compliant, user should expect undefined behavior, which includes successful or unsuccessful indexing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as we don't serialize non-compliant values and there's no panic, this sounds fine. Ideally, we would increment the dropped attributes count.