feat(pino-transport): Add functionality to send logs to sentry

[AbhiPrasad]

ref #15952

resolves #16622

This PR adds the ability to send logs to sentry via a pino transport.

Usage

import pino from 'pino';

const logger = pino({
  transport: {
    target: '@sentry/pino-transport',
    options: {
      // Optional: filter which log levels to send to Sentry
      logLevels: ['error', 'fatal'], // defaults to all levels
    },
  },
});

// Now your logs will be sent to Sentry
logger.info('This is an info message');
logger.error('This is an error message');

Options

logLevels

Type: Array<'trace' | 'debug' | 'info' | 'warn' | 'error' | 'fatal'>

Default: ['trace', 'debug', 'info', 'warn', 'error', 'fatal'] (all levels)

Use this option to filter which log levels should be sent to Sentry.

const transport = pino.transport({
  target: '@sentry/pino-transport',
  options: {
    logLevels: ['warn', 'error', 'fatal'], // Only send warnings and above
  },
});

Next

I need to write some integration tests - this is being tracked by #16624

[AbhiPrasad]

I'm still undecided about this behaviour.

See https://getpino.io/#/docs/api?id=opt-customlevels for details about pino custom levels.

What does everyone think?

[s1gr1d]

Do you mean the level ranges?

Currently, you're "cutting" it in the middle of the range (or are those already the Pino level cuts?). How about cutting it at the point where the level changes? Like this:

• 0-19 → trace
• 20-29 → debug
• 30-39 → info
• 40-49 → warn
• 50-59 → error
• 60+ → fatal

But I am not quite sure how pino works here 🤔

[chargome]

Bit hard to map, your call!

[AbhiPrasad]

How about cutting it at the point where the level changes

I think that feels better, just tried it out in my test app. Feels easier to explain to users as well.

[s1gr1d]

Do you mean the level ranges?

Currently, you're "cutting" it in the middle of the range (or are those already the Pino level cuts?). How about cutting it at the point where the level changes? Like this:

• 0-19 → trace
• 20-29 → debug
• 30-39 → info
• 40-49 → warn
• 50-59 → error
• 60+ → fatal

But I am not quite sure how pino works here 🤔

[chargome]

Bit hard to map, your call!