Add others tracing protocol's capabilities and documentation.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
## Feature Request
### What problem are you trying to solve?
Increase documentation on OpenCencus Collector to add Zipkin and Jaeger tracing endpoints capabilities, put these options in the documentation, the OpenCencus Protocol misses a lot of clients or projects without maintenance (because of opentelemetry merge) to send application trace.
### How should the problem be solved?
Give clearly alternatives to OpenCensus Protocol to trace in the application.
### Any alternatives you've considered?
Change all to OpenTelemetry project
### How would users interact with this feature?
Clear the way to implement trace more easily.
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 OpenCensus Collector documentation and the requested Zipkin and Jaeger tracing endpoint capabilities. Done means the documentation clearly presents these alternatives for sending application traces, including the relevant capabilities and implementation guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100