-
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] Bulk indexer error: an id must be provided if version type or value are set #33139
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
anyone can take a look for this issue? |
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. |
does anyone knows the solution ? |
@lmssy |
Sorry for the late reply. I am unable to reproduce the issue with v7.17.23 Elasticsearch and v0.108.0 elasticsearchexporter with a simpler config:
Questions
|
I encountered the same error when using ES V7.3.2, but upgraded ES to V7.17.24 and restored it to normal |
I managed to reproduce this. It is because in version ES 7.3.2, bulk API This issue is good to close. |
Component(s)
exporter/elasticsearch
What happened?
Description
I'm trying to export trace & span to elasticsearch v7, I config collector just follow the document https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/elasticsearchexporter
but in collector's log report below error, there is no index created in elasticsearch. please help to check, thx.
Steps to Reproduce
Expected Result
Actual Result
Collector version
0.100.0
Environment information
Environment
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: