Support distributed tracing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
If distributed tracing is supported by a Central Dogma server, users can easily find a performance bottleneck in their request paths and visualize the dependencies of the Central Dogma server.
We will define a configuration for `distributedTracing` and make the server report tracing information based on that.
```json
{
"distributedTracing": {
"collectorUrl": "http://127.0.0.1:.../api/../spans",
"serviceName": "CentralDogma",
"samplingRate": "0.01",
...
}
}
```
A builder API can be also used to configure distributed tracing for both a server and a client.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing server and client configuration and builder APIs, since the issue proposes changes to both. Define the distributedTracing configuration around collectorUrl, serviceName, and samplingRate, then verify that the server reports tracing information and that the configuration is usable through both builders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100