export metrics around tokio scheduling

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #162 by @DivyamTalwar — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
observability

Research direction

The issue names no files. It points to the tokio-metrics crate (docs.rs/tokio-metrics) and a related foyer PR comment for context. Start by finding where the project already exposes metrics, then check how tokio-metrics collects runtime stats. Done means Tokio scheduling metrics show up in the same metrics output as the existing ones. Settle which metrics to export before writing code, since the issue does not say.

Written by the indexing model from the issue text.

Description

Dominant language
Rust
Stars
622
Forks
18
Avg merge
19h 18m
Merged PRs (30d)
31

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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.

More from s2-streamstore/cachey

All issues in s2-streamstore/cachey

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.