-
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] Create micro-benchmarks for mapping.mode: ecs
field conversions
#32746
Comments
cc: @axw |
Pinging code owners for exporter/elasticsearch: @JaredTan95 @ycombinator @carsonip. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was filed by a code owner, so I'm removing |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/elasticsearch
Is your feature request related to a problem? Please describe.
When
mapping.mode: ecs
is used, certain OTel + SemConv fields are converted to ECS fields to ensure that dashboards and other assets currently using ECS fields continue to work. This conversion, at scale, could prove to be expensive.Describe the solution you'd like
It would be good to have micro-benchmarks in place exercising the conversion code to ensure they do not become too expensive at scale.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: