stackabletech / stackabletech/tokio-zookeeper

Replace slog with tracing

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

release-note/action-required type/internal-debt
Dominant language
Rust
Stars
78
Forks
22
PR merge metrics
No merged PRs in 30d

Description

Tracing is far more common in the wider Tokio ecosystem these days, so it makes sense to log where people are looking for it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the repository's slog usage and tracing-related configuration, then determine the full scope of the replacement; done means logging uses tracing consistently and the project still builds and its tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
observability
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.