[Feature]: Support Elasticsearch/OpenSearch data stream

Description

Contributor guide

Tech stack

goelasticsearch

Domain

backenddatabaseobservability

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

5

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

over 1 week

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

Jaeger storage architectureElasticsearch data streamsGo knowledge

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

20

Research direction

Review Jaeger's existing Elasticsearch storage implementation in the 'plugin/storage/es' directory. Study Elasticsearch/OpenSearch data stream APIs and index lifecycle management. Examine the related issue #7150 for prior discussion and requirements. Investigate how to map Jaeger's trace data (spans, services) to data stream indices, ensuring compatibility with existing index templates and rollover policies.