Best practices for scoped logging

Hi Probot friends!

I’m working on a bot that reacts to pull request events. For debugging purposes, I’d like to be able to tail Probot’s logs and grep for log lines that pertain to just that PR:

heroku logs -t | grep pr-123

At present, I’m thinking of creating a custom logging function in the scope of the event handler:

async function handler (context) {
  function log (args) {
    const prefix = `pr-${context.payload.pull_request.number}`
    context.log(prefix, ...args)
  }

  log('some', objects, and, stuff)
})

Is there a better built-in way to includ grep-friendly context when logging?

cc @sarahs

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label question ❓ to this issue, with a confidence of 0.83. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[gr2m]

Probot is using pino internally now, all instances should have the .child() method, see https://getpino.io/#/?id=usage

<div>Pino - Super fast, all natural JSON logger for Node.js</div><div>Super fast, all natural JSON logger for Node.js</div>