Skip to main contentConduktor helps you detect and enforce data quality standards for messages flowing through Kafka.
How it works
You create Rules that define the expected format and content of messages, then attach them to Policies that target specific Kafka topics or topic prefixes.
Conduktor evaluates these Rules against every message produced on targeted topics after Policy creation and tracks the count of violating messages as well as the total number of messages evaluated.
Observe vs. enforce
The capabilities depend on whether you’re using Gateway:
Without Gateway (observe only)
- Records are verified after they have been produced
- Track violations and monitor data quality issues
- No impact on message flow
With Gateway (observe and enforce)
- Records are verified before production
- Take action on faulty records:
- Block: reject the message (and the entire batch). The producer will fail with an error message
- Mark: add a header to the record containing all violated rules for every Policy using the mark action
- Prevent bad data from entering your topics
Key constraints
- Policies cannot mix different target cluster types (Gateway vs. non-Gateway)
- You can’t target a Gateway-backing cluster directly to avoid validation conflicts
