17:42:05.326Z DEBUG Probot: Comment created
    event: {
      "id": "4cfd3e80-c575-11e7-8e7b-a2d9629ce9eb",
      "event": "issue_comment",
      "action": "created",
      "repository": "robotland/test",
      "installation": 13055
    }

I'm not crazy about how verbose every log comment will be because of this.

One idea: update the serializers to include more/less context based on LOG_LEVEL. I'm thinking that LOG_LEVEL=debug would be the trigger that causes serializers to show more context.

The tough part with logging is that, in production, you only need it when somethings gone wrong and you want to find out why. I've experienced that, and often I look through my webhook deliveries on the GH UI for:

• Repository
• Payload ID
• Event

I think that LOG_LEVEL=debug can be more verbose, but I can see myself getting value from having those three present in a production logger.

It also doesn't necessarily need to be wrapped in the event: {} object as far as the logs are concerned; to save on precious terminal space it could look like:

17:42:05.326Z DEBUG Probot: Comment created
---
id: 4cfd3e80-c575-11e7-8e7b-a2d9629ce9eb
event: issue_comment.created
repository: robotland/test

With the values in bold (using chalk or something)

It also doesn't necessarily need to be wrapped in the event: {} object as far as the logs are concerned; to save on precious terminal space it could look like:

We don't currently have a lot of control over this. We're currently using https://github.com/thlorenz/bunyan-format, which we can make improvements to later.

GitHub

thlorenz/bunyan-format

bunyan-format - Writable stream that formats bunyan records that are piped into it