jaegertracing/jaeger

ES storage plugin: query service to support spanKind when retrieve operations for a given service

Open

#1923 opened on Nov 13, 2019

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
good first issuehelp wantedstorage/elasticsearch

Description

Requirement - what kind of business use case are you trying to solve?

Related to #1920

Update ElasticSearch reader and writer such that we can retrieve operations by service name and span kind

Problem - what in Jaeger blocks you from solving the requirement?

Proposal - what do you suggest to solve the problem or improve the existing situation?

Any open questions to address

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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingElasticsearch knowledgeJaeger storage plugin architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The issue requires modifying the ElasticSearch storage plugin to support filtering operations by spanKind. Start by examining the existing operations retrieval logic in the ES reader, likely in `plugin/storage/es/` directory. Reference issue #1920 for additional context. The implementation should update both the reader and writer to index and query spanKind. Review comments on this issue for any additional requirements.