Thanks to visit codestin.com
Credit goes to github.com

Skip to content

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

Merged
AbhiPrasad merged 9 commits intodevelopfrom
abhi-pino-logs-impl
Jun 24, 2025
Merged

feat(pino-transport): Add functionality to send logs to sentry#16667
AbhiPrasad merged 9 commits intodevelopfrom
abhi-pino-logs-impl

Conversation

@AbhiPrasad
Copy link
Contributor

@AbhiPrasad AbhiPrasad commented Jun 20, 2025 •
edited
Loading

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 AbhiPrasad self-assigned this Jun 20, 2025
@AbhiPrasad AbhiPrasad force-pushed the abhi-pino-logs-impl branch from 4661a26 to ad39866 Compare June 20, 2025 15:54
AbhiPrasad
AbhiPrasad commented Jun 20, 2025
View reviewed changes
packages/pino-transport/README.md
| error | 50 | error |
| fatal | 60 | fatal |

### Custom Levels Support
Copy link
Contributor Author

@AbhiPrasad AbhiPrasad Jun 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Member

@s1gr1d s1gr1d Jun 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 🤔

Copy link
Member

@chargome chargome Jun 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bit hard to map, your call!

Copy link
Contributor Author

@AbhiPrasad AbhiPrasad Jun 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@AbhiPrasad AbhiPrasad marked this pull request as ready for review June 20, 2025 15:58
@AbhiPrasad AbhiPrasad requested review from a team, Lms24 and s1gr1d and removed request for a team June 20, 2025 15:58
s1gr1d
s1gr1d approved these changes Jun 24, 2025
View reviewed changes
packages/pino-transport/README.md
| error | 50 | error |
| fatal | 60 | fatal |

### Custom Levels Support
Copy link
Member

@s1gr1d s1gr1d Jun 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
chargome approved these changes Jun 24, 2025
View reviewed changes
packages/pino-transport/README.md
| error | 50 | error |
| fatal | 60 | fatal |

### Custom Levels Support
Copy link
Member

@chargome chargome Jun 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bit hard to map, your call!

@AbhiPrasad AbhiPrasad force-pushed the abhi-pino-logs-impl branch from 398fe71 to 4f3435a Compare June 24, 2025 15:22
@AbhiPrasad AbhiPrasad force-pushed the abhi-pino-logs-impl branch from 4f3435a to 57434de Compare June 24, 2025 15:23
@AbhiPrasad AbhiPrasad merged commit 3c012d0 into develop Jun 24, 2025
163 checks passed
@AbhiPrasad AbhiPrasad deleted the abhi-pino-logs-impl branch June 24, 2025 19:43
@github-actions github-actions bot mentioned this pull request Jun 25, 2025
Closed
@micahjon micahjon mentioned this pull request Aug 24, 2025
Closed
This was referenced Sep 29, 2025
Closed
Closed
This was referenced Oct 7, 2025
Closed
Closed
@fossabot fossabot bot mentioned this pull request Oct 15, 2025
Closed
@fossabot fossabot bot mentioned this pull request Oct 21, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@chargome chargome chargome approved these changes

@s1gr1d s1gr1d s1gr1d approved these changes

@Lms24 Lms24 Awaiting requested review from Lms24 Lms24 was automatically assigned from getsentry/team-javascript-sdks

Assignees

@AbhiPrasad AbhiPrasad

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Implement logs pino support via pino-abstract-transport

3 participants

@AbhiPrasad @chargome @s1gr1d