fix: improve startup diagnostics and Redis resilience - #55
Merged
Conversation
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.
Improve daemon startup diagnostics while keeping emitted startup configuration limited to an explicit safe allowlist. Fatal errors now follow etl-replicator's typed
main -> try_main -> render_reportflow, including categorized source-chain reports and optional backtraces.Safe Startup Visibility
Startup emits one INFO event containing only the stream ID, sink type, batch settings, and TLS state. Sink identity uses the same config-level
kind()pattern as etl-replicator destinations, covering every feature-gated sink without logging sink configuration.Redis Resilience
Redis Strings and Redis Streams now support connection/response timeouts and reconnect controls. Redis failures preserve their source and distinguish transient connectivity/capacity errors, authentication failures, and permanent client/data errors so ETL can apply the appropriate retry policy.