Open ninjatux opened 8 years ago
If I understand this correctly, when (and only when) this is done, we may no longer need the slack and mail dev warnings, so we can remove all that stuff. See #35
When logging errors, let's always include the full error message with stack traces and also the commit hash of the app the packer was serving when the error occurred (helps with debugging problems with the app itself which makes the packer's job impossible, producing the error)
We need to be able to chose and configure the logger transport. I suggest to use
bunyan
logger which implementsdtrace
by default and makes it easy to inject different type of transporters.We should make the packer able to log by default in
STDOUT
and if configured also overTCP
,UDP
orFILE
. Would be nice in the future have a central repositories for logs, eg: loggly, logentries or an open source solution like logio