jaegertracing/jaeger

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

Open

#1922 opened on Nov 13, 2019

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

Description

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

Related to #1920

Update badger 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
go
Domain
backenddatabase
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.
1-2 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.
needs investigation
Prerequisites
Go programmingJaeger tracing platformbadger key value storespanKind concept in tracing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Start by examining the badger storage plugin code in the Jaeger repository, focusing on the reader and writer implementations. Review issue #1920 for context on spanKind support. Look through the comments in this issue for any additional guidance from maintainers. The goal is to update the operations query to support filtering by spanKind, which may involve modifying the data model and query logic in the badger plugin.