Momentum#1472 document the %OC custom_logger macro - #865
Merged
Conversation
…he mainlog connection-ID fields custom_logger gains %OC (outbound connection ID) so custom formats can match what ec_logger writes in the mainlog connection field on D/T/P records without changing what %CI has always meant. Clarify %CI as the inbound connection ID, and spell out inbound vs outbound for the four mainlog connection-ID rows. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for support-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dkoerichbird
approved these changes
Aug 6, 2026
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
2 participants
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.
What
%OCmacro to the custom_logger module docs: the outbound connection ID, i.e. the value ec_logger writes in the mainlog connection field on delivery, transient-failure and permanent-failure records. Notes that each delivery attempt uses a new connection (retries log different values) and that it expands empty on receptions.%CIas the inbound connection ID, with a cross-reference to%OC.Why
%OCis added in SparkPost/Momentum#1472 so custom log formats can reproduce the mainlog's connection field on delivery-side events without redefining%CI, which on-premise customers already consume as the inbound connection ID.Note for review:
%OCfirst ships in 5.3.0 — if these momentum/4 pages need a version annotation or a different home per the docs versioning convention, happy to adjust.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only updates to Momentum 4 logging reference pages; no runtime or configuration behavior changes in this repo.
Overview
Documents the new
%OCcustom_logger format macro (outbound connection ID) and clarifies how connection ID fields in the mainlog differ between inbound and outbound events.In
custom-logger.md,%CIis now described explicitly as the inbound connection ID (mainlog reception records), with a pointer to%OCfor delivery-side connection IDs.%OCis added to the format specifier list: outbound connection used for a delivery attempt, matching mainlog D/T/P records, empty on receptions, and a new value per retry.In
log-formats-mainlog.md, offset-3 Connection ID descriptions are updated for reception (inbound), delivery, transient failure, and permanent failure (outbound, new connection per attempt).Reviewed by Cursor Bugbot for commit f0a4458. Bugbot is set up for automated code reviews on this repo. Configure here.