For the application process please refer to this issue.
- Description: Jaeger has always supported Elasticsearch (ES) as an official backend. Unfortunately, the Go driver we are using,
olivere/elastic, does not support ESv8 and not planning to release any new versions. Despite the licensing changes, Elasticsearch remains a popular choice and v8 support question often comes up. In this project we want to add official support for ESv8. However, we also want to take this opportunity to do a better alignment with OpenTelemetry Collector, which already has an ESv8 exporter, perhaps we can use it directly and minimize the amount of code.
- Expected Outcomes:
- Use OTEL ESv8 exporter from Jaeger, if possible, otherwise build internal implementation
- Stretch goal: use ES data as the source for Jaeger SPM views
- Recommended Skills:
- Go:
go.mod, bing able to understand existing code, coding, testing ,refactoring
- Elasticsearch: understand ES architecture, shards, replicas, inserting data, searching for data, indices, index templates, index aliases, index rotations
- Mentor(s):
- Mentee:
Related: #3571
Resources
For the application process please refer to this issue.
olivere/elastic, does not support ESv8 and not planning to release any new versions. Despite the licensing changes, Elasticsearch remains a popular choice and v8 support question often comes up. In this project we want to add official support for ESv8. However, we also want to take this opportunity to do a better alignment with OpenTelemetry Collector, which already has an ESv8 exporter, perhaps we can use it directly and minimize the amount of code.go.mod, bing able to understand existing code, coding, testing ,refactoringRelated: #3571
Resources