feat: configurable log levels for pulse and provision events#67
Merged
Conversation
New LogLevelConfig options on PathwaysBuilder:
- pulseSuccess (default: 'debug') — successful pulse emissions
- pulseFailure (default: 'warn') — pulse emission failures
- provisionSuccess (default: 'info') — virtual pathway registered
- provisionFailure (default: 'error') — virtual pathway registration failed
Structured context added to provision() logs:
- success: { pathwayName, pathwayId, status, flowTypes }
- failure: { pathwayName, url, status, body, phase } (now logged
BEFORE the throw so NoopLogger consumers still get the crash message
but structured loggers capture full context)
Log levels propagated through PathwayPumpOptions.pulse to the
data-pump PulseEmitter (requires @flowcore/data-pump with matching
pulse log level support).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends
LogLevelConfigwith four new optional fields and adds structured logging to pulse and provision events.New config (
LogLevelConfig):pulseSuccessdebugpulseFailurewarnprovisionSuccessinfoprovisionFailureerrorProvision logging:
logger[provisionSuccess]("Virtual pathway registered", { pathwayName, pathwayId, status, flowTypes })logger[provisionFailure]("Virtual pathway registration failed", { pathwayName, url, error, phase: "network" })before throwlogger[provisionFailure]("Virtual pathway registration failed", { pathwayName, url, status, body, phase: "response" })before throwPulse logging (via data-pump):
PathwayPumpOptions.pulse.successLogLevel/failureLogLevelto the data-pumpPulseEmitterWhy:
NoopLoggerconsumers (e.g. usable-chat) had zero visibility into provision/pulse failures. Now structured context is logged via the configured logger at configurable severity.Requires
@flowcore/data-pumpwith matchingPulseEmitterlog level support (PR feat: configurable log levels for pulse success and failure data-pump#68)Test plan
deno checkcleandeno lint+deno fmtclean🤖 Generated with Claude Code