logging could use some centralization

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend, observability

Research direction

Review the two current log locations: /home/pushserver/logs/pushserver/push_server and /home/pushserver/logs/supervisor/pushserver_stdout. Trace where the pushserver and supervisor logging are configured, then determine how errors and exceptions should reach Sentry and how info-level logs should be consolidated. Done means both logging destinations are addressed and the intended Sentry reporting works.

Written by the indexing model from the issue text.

Description

The pushserver is logging in a few different places:
/home/pushserver/logs/pushserver/push_server - mostly messages about deleted subscriptions
/home/pushserver/logs/supervisor/pushserver_stdout - mostly db logs for subscription INSERTs and SELECTs

It would be nice to push errors and exceptions to Sentry (and centralize the info-level logs in one file on the app server if possible)

Dominant language
JavaScript
Stars
30
Forks
8
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 EFForg/pushserver

All issues in EFForg/pushserver

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.