Improve logging through syslog

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

The payload names no files, tests or entry points, so begin by finding where the project currently emits its Python log output. The issue never says which components should log to syslog or what format to use, so the scope must be agreed with maintainers first. Done means a settled design and a working syslog handler, with the change confirmed by a maintainer.

Written by the indexing model from the issue text.

Description

enhancement

Per our conversation during the open period LMG1906, we suggest that consistent logging through the syslog facility will improve troubleshooting. Eventually, troubleshooting will fall to the poor saps on the vessels when things go wrong. They'll be more like to find the information they need if it is in one place they should already be familiar with.

Dominant language
Python
Stars
57
Forks
30
Avg merge
3h 14m
Merged PRs (30d)
56

Getting set up

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 OceanDataTools/openrvdas

All issues in OceanDataTools/openrvdas

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.