jaegertracing/jaeger

[v2] How is tenancy handled / configured? Should it be part of storage config?

Open

#6,108 opened on Oct 22, 2024

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
area/storagegood first issuehelp wantedv2

Description

This might just need some verification / findings, with code links.

Contributor guide

Tech stack
go
Domain
backendinfrastructure
Issue type
research
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.
half day
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
Basic Jaeger knowledgeMulti tenancy concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the Jaeger v2 storage configuration code to determine if tenancy is currently handled and where. Look at the storage configuration structs and any existing tenancy fields. Review related discussions in the issue comments for context. Provide a summary of findings and suggest a direction for design.