Consider replacing Jaeger with Tempo for better Grafana integration
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Decided to go with [Jaeger](https://www.jaegertracing.io/) originally out of habit, but the integration into Grafana is a bit clunky not being able to display trace information outside of the explore view. Consider swapping this for [Grafana Tempo](https://grafana.com/oss/tempo/) instead which integrates much more cleanly into Grafana, will create separate issue for introducing Loki as the tooling for logs.
Contributor guide
Research direction
Review the repository for the current Jaeger configuration and Grafana integration; the issue does not name specific files or tests. Compare the existing setup with Grafana Tempo's integration requirements, and consider the work complete when tracing is provided through Tempo and the Grafana experience is improved as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, grafana
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100