Print messages from Iggy streams to standard output, for debugging and verifying a connector pipeline.
The stdout sink connector prints messages from Iggy streams to the standard output. This is useful for debugging, development, and verifying that your connector pipeline is working correctly.
The connector emits info-level tracing events through the runtime to stdout. The runtime selects text or JSON with logging.format and filters events with RUST_LOG (default INFO). It logs batch metadata on every invocation; print_payload additionally logs each message's offset and decoded payload. The invocation counter is in memory and resets when the plugin is recreated.
Configuration
Use the broker credentials and runtime setup from the sink guide. Save the configuration below in that runtime's connector directory. From the matching 0.9.0/edge repository root, build the plugin:
cargo build --release -p iggy_connector_stdout_sinktype = "sink"
key = "stdout-sink"
enabled = true
version = 1
name = "Stdout Sink"
path = "target/release/libiggy_connector_stdout_sink"
verbose = false
[[streams]]
stream = "my-stream"
topics = ["my-topic"]
schema = "json"
batch_length = 10
poll_interval = "1s"
consumer_group = "stdout-sink-group"
[plugin_config]
print_payload = truePlugin config options
| Option | Type | Default | Description |
|---|---|---|---|
print_payload | bool | false | Whether to print the message payload to stdout |
Create my-stream and my-topic before starting the runtime, or change the sample to use existing resources. The Random source configuration produces JSON to the same destination.
