[Feature Request]: Supporting opentelemetry as config defaults

[JPeer264]

🔎 Search Terms

opentelemetry, otel, config defaults

The vision

There are couple of defaults already supported by winston, such as npm, cli, syslog. But OpenTelemetry is not one of them. OpenTelemetry has different levels than the others, including fatal and trace as a name.

The usage of OpenTelemetry is increasing, which indicates a strong adoption into this direction.

Also it got me thinking to add this here since in Sentry we got an issue getsentry/sentry-javascript#18868 for this and was thinking were it would make the most sense.

Solution

• Supporting .fatal() and .trace() in winston as one of the logmethods
• Adding a new config default for opentelemetry as for npm and others

Use case

The use case is pretty straight forward. If you are working with OpenTelemetry you want to use the same levels as their standard

Additional information

FWIW OpenTelemetry has more severity numbers for each level. Here it could be worth to check out for pinos integration: https://github.com/pinojs/pino-opentelemetry-transport/blob/37e01c31b76d2dd27b1a99fe89da12f0cb52625a/lib/opentelemetry-mapper.js#L8-L15