Print messages to logs for debugging and inspection

Use This When

• Debugging pipelines to verify message content and flow at specific points
• Validating data transformations by inspecting intermediate results
• Capturing sample messages for documentation or test case creation
• Troubleshooting type mismatches or unexpected data structures

What It Does

• Prints each incoming message to stdout with sequential index counter
• Passes through message without modification (sink component with no output)
• Displays full message content including nested structures and type information
• Increments counter for each message to track sequence order

Works Best With

• Any component during development → this component for inspection
• Placed between transforms to verify data shape changes
• Integration with platform log capture for persistent message history
• Debugging workflows where visual inspection of data is needed

Caveats

• No output stream; acts as terminal sink removing messages from pipeline
• Logs ephemeral unless platform captures stdout; configure log persistence if needed
• High message rates produce verbose output; use limit-message-rate upstream if needed
• Large messages with images or tensors create very long log lines