oxidecomputer / oxidecomputer/dropshot
Generalize dtrace support for other tracing tools
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 104
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
Hi! I really like the dtrace support built into dropshot. Obviously there are personal and historical reasons why dropshot has first-class support for dtrace ;) But I'd like to include other tracing mechanisms in my Dropshot server.
It would be great if the dtrace support wasn't a "special case" built into the framework, but rather, the framework allowed a "tracing trait" which has an implementation for dtrace. Then users could implement that trait for
- sentry
- jaegar
- whatever tracing their project uses
@jessfraz and I would be happy to open a PR for this to explore a prototype, if y'all agree that this general idea is desirable :)
Contributor guide
No contributing guide indexed for this repository
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 locating Dropshot's existing dtrace support and the framework entry points where tracing behavior is defined. Compare the proposed tracing trait with the current dtrace-specific design and determine how a dtrace implementation and user-defined implementations would fit. Done should include an agreed abstraction and a working dtrace implementation, with the scope settled before coding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100