jaegertracing/jaeger

[Feature]: Support Elasticsearch/OpenSearch data stream

Open

#4,708 opened on Aug 29, 2023

View on GitHub
 (61 comments) (14 reactions) (0 assignees)Go (2,326 forks)batch import
area/storageenhancementhelp wanted

Repository metrics

Stars
 (18,974 stars)
PR merge metrics
 (Avg merge 5d 7h) (75 merged PRs in 30d)

Description

Summary

Data streams are the new hotness in Elasticsearch & OpenSearch to store append-only observability data. Data streams are well-suited for logs, events, metrics, and other continuously generated data.

Requirement

Proposal

No response

Related issues

  • #7150

Contributor guide

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.
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