jaegertracing/jaeger

Storage backends for adaptive sampling

Open

#3,305 opened on Oct 5, 2021

View on GitHub
 (20 comments) (4 reactions) (1 assignee)Go (18,974 stars) (2,326 forks)batch import
help wanted

Description

Since v1.27 adaptive sampling is supported in the backend, but it only works with Cassandra as the backing store. We need to implement it for other types of stores, e.g.

  • memory-only (for all-in-one) #3335
  • Badger #4834
  • Elasticsearch #5158
  • OpenSearch
  • gRPC remote storage
  • Documentation once all of the above are done

Contributor guide

Tech stack
gogrpc
Domain
backenddatabaseobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
clear
Prerequisites
Understanding of Jaeger adaptive samplingFamiliarity with gRPCGo programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Review the existing adaptive sampling implementations for memory only (#3335), Badger (#4834), and Elasticsearch (#5158) to understand the storage backend pattern. Then implement the gRPC remote storage backend, following the same approach. The issue notes that documentation is also needed after all backends are done.