oxidecomputer / oxidecomputer/omicron
want cockroachdb logs to be found via `svcs -L` and rotated/archived
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently cockroachdb logs to various files in /data/logs inside its zone, which is not a path listed by svcs -L (where we often look first) and is not part of our current log rotation/archival configuration.
Ideally, cockroachdb would be logging to stdout/stderr, so that its output is captured in the SMF log and is rotated and archived along with all the other service logs across the system. It does log to multiple files for different reasons, so that may complicate things.
Contributor guide
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 tracing how cockroachdb logging is configured inside its zone, including the /data/logs files, the SMF service output, and the existing rotation and archival configuration. Done means cockroachdb output is discoverable through svcs -L and its relevant logs are rotated and archived with the other service logs.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100