logging to filesystem

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the logging implementation and the current ringbuffer and stdout logging paths. Determine how filesystem logs would remain visible through zinit and how their size should be bounded; done means logs are persisted without unbounded growth while retaining the existing display behavior.

Written by the indexing model from the issue text.

Description

ability to log to filesystem, now its in ringbuffer or stdout
also make sure log cannot get too big

if we do to filesystem the zinit logs... should still show

Dominant language
Rust
Stars
16
Forks
2
No merged PRs in 30d

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.

More from threefoldtech/zinit

All issues in threefoldtech/zinit

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.