KillingSpark / KillingSpark/rustysd

Logging

Open
#21 16 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
579
Forks
19
PR merge metrics
No merged PRs in 30d

Description

Rustysd needs persistent logging. This needs some questions answered:

1. Should rustysds logs go somewhere else than stdout/stderr output of services?
2. Should each service have it's own log or should it all be in one file?
3. Can/Should rustysd just reuse systemd-logind?

Update: I meant systemd-journald of course!

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by resolving whether logs should remain on service stdout/stderr, be split per service or combined, and whether systemd-journald should be reused; done means the logging design and persistent behavior are clearly defined and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.