What problem does it solve?
Diagnoses, validates, and monitors Redpanda Connect pipelines. Use when a
Redpanda Connect pipeline fails, stalls, drops messages, or won't start; when
linting a config with rpk connect lint; tuning log level or format; reading
Connect metrics (Prometheus, statsd, json_api) or traces (OpenTelemetry);
checking /ready and /ping health endpoints; running a dry-run connection test;
or diagnosing connector failures including auth errors, TLS errors, Enterprise
license errors, backpressure, and checkpoint/cache issues. Covers Redpanda
Connect enterprise features and their config keys: enterprise connectors
including all CDC inputs (postgres_cdc, mysql_cdc, mongodb_cdc, oracledb_cdc
logminer block), connector allow/deny lists, secrets management URNs, the
redpanda: configuration service block, and FIPS compliance — all requiring an
Enterprise license.
Core Features & Use Cases
- Diagnoses, validates, and monitors Redpanda Connect pipelines for resilience.
- Provides linting, dry-run validation, health checks, metrics, and tracing visibility.
- Supports enterprise feature awareness, including license and access controls.
Quick Start
Run rpk connect lint on your pipeline YAML, then perform a dry-run to validate connections and use health and metrics endpoints to diagnose issues.
