Skip to content
This repository has been archived by the owner on Mar 4, 2018. It is now read-only.

Logging #43

Open
elijahverdoorn opened this issue Oct 27, 2017 · 2 comments
Open

Logging #43

elijahverdoorn opened this issue Oct 27, 2017 · 2 comments
Assignees
Milestone

Comments

@elijahverdoorn
Copy link
Member

We should at least think about if we want to keep logs of events in our final version, especially given that this is a somewhat critical system and it would be nice to know what went wrong, if something ever were to go badly.

I might suggest that we look at morgan, which plays nicely with express.

@elijahverdoorn elijahverdoorn self-assigned this Oct 27, 2017
@elijahverdoorn
Copy link
Member Author

(and yes, I know morgan is already in the package. It comes with express-generator. We should be considering if we want to use it or remove it.)

@rye
Copy link
Contributor

rye commented Oct 30, 2017

I like the idea of logging http requests through morgan.

I would also like performance monitoring on DB reads/writes, and general event logging. These should be separate log streams but be aggregated together.

I like the idea of writing to syslog, too, though I don't know if we'd be able to get logs rotated elsewhere.

@rye rye added this to the Version 1.0 milestone Jan 12, 2018
@rye rye modified the milestones: Version 0, Version 1 Feb 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants