Logger
Category: Monitoring
Node id: logger
Provides structured logging with buffering, querying, and multiple output destinations
What it does
- Structured logging with JSON, text, and structured output formats
- Log levels: debug, info, warn, error, fatal
- Multiple output destinations: stdout, stderr, discard, or file path
- Log buffering with flush, query, and clear operations
- Contextual fields, tags, trace ID, and span ID attachment
- Query buffered logs by level and message substring filters
Use cases
- Log pipeline step results for debugging and audit trails
- Buffer logs during batch processing and flush at completion
- Write structured JSON logs to file for external log aggregation
- Attach distributed tracing context (trace_id, span_id) to log entries
- Query buffered logs to generate pipeline execution summaries
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
message | any | No | Log message (overrides config message) |
context | json | No | Contextual data to attach to the log entry |
fields | json | No | Structured fields to attach to the log entry |
tags | json | No | Tags to attach to the log entry |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Full log result with entries, summary, and metadata |
logged | boolean | No | Whether the message was written immediately |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | No | log | log, debug, info, warn, error, fatal, buffer, flush, query, clear | Logging operation to perform |
| Level | level | enum | No | info | debug, info, warn, error, fatal | Log severity level |
| Format | format | enum | No | json | json, text, structured | Log output format |
| Message | message | text | No | Static log message (overridden by input) | ||
| Output Destination | output | string | No | stdout | Output destination (stdout, stderr, discard, or file path) |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Trace ID | trace_id | string | No | Distributed trace ID to attach | ||
| Span ID | span_id | string | No | Span ID to attach | ||
| Fields | fields | json | No | Static structured fields | ||
| Tags | tags | json | No | Static tags | ||
| Level Filter | level_filter | string | No | Filter buffered logs by level (query operation) | ||
| Message Filter | message_filter | string | No | Filter buffered logs by message substring (query operation) | ||
| Limit | limit | number | No | 100 | Maximum entries to return (query operation) |
Errors
| Code | Description |
|---|---|
MISSING_MESSAGE | Log message is required but was not provided in config or input |
UNSUPPORTED_OPERATION | Operation is not one of the supported logging operations |
UNSUPPORTED_FORMAT | Log format is not one of: json, text, structured |
LOG_WRITE_FAILED | Failed to write log entry to the configured output destination |
Runtime notes
- logged=false for buffer/query/clear operations — the message is held in memory, not written
- Buffer is in-memory and per-node-instance; use flush to write all buffered entries at once
- result.entry is present for single-log operations; result.entries is present for flush/query
- File output destinations auto-create parent directories and append to existing files
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..