-
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] Use a single instance of esExporter
for all event types
#33326
Comments
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
Describe the issue you're reporting
With #33318 both logs and traces exporter will be unified to use the newly introduced
esExporter
, however, it will still create a new instance of theesExporter
for each event type. This leads to additional overhead to maintain more bulk indexers. Refactor the code using SharedComponent or a similar method to create a single instance of theesExporter
for all event types.The text was updated successfully, but these errors were encountered: