Add LoggerProvider support to @effect/opentelemetry
#4371
Conversation
🦋 Changeset detectedLatest commit: 67ebeef The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Working on tests and docs before removing draft status |
jpowersdev
changed the title
LoggerProvider support to @effect/opentelemetry
|
I tried to follow the existing structure as best I could, but please let me know if anything needs to be modified. |
| ) | ||
|
|
||
| /** @internal */ | ||
| const formatMessage = Match.type<unknown>().pipe( |
There was a problem hiding this comment.
I think instead we can reuse this
Using the Match module is a bit too much here.
There are probably other functions that could be moved to a utils module
| severityText: structured.logLevel, | ||
| severityNumber: options.logLevel.ordinal, | ||
| timestamp: options.date, | ||
| observedTimestamp: new Date(), |
There was a problem hiding this comment.
This should use the clock service instead.
| * @since 1.0.0 | ||
| * @category layers | ||
| */ | ||
| export const layerLoggerProvider = ( |
There was a problem hiding this comment.
This should be a direct export instead of a wrapper function
Type
Description
Add
LoggerProviderandLogRecordProcessorsupport to@effect/opentelemetry, as well as a logger layer (usingLogger.addEffectto run alongside existing loggers) that will emit logs using the registeredLogRecordProcessor.