A subscription pattern
Which topics a regex subscription matches, and when the consumer notices a new one
orders.created orders.shipped orders-legacy inventory.updated
Kafka Topic Regex Subscription Tester
Test a Kafka pattern subscription against a list of topic names. Anchored at both ends, because Kafka calls Matcher.matches(), and every construct where Java's regex differs from JavaScript's is reported rather than glossed over.
Do not add ^ and $: Kafka matches the whole
name already, and this page anchors the pattern for you so what you see is
what the consumer would subscribe to.
Paste below, or drop a file anywhere on this panel
Or drop a file anywhere on this panel. Nothing is uploaded: the analysis runs in this tab.
The answer appears here
Paste on the left and press Test pattern. Nothing leaves this tab.
Formatted
Results
Nothing else to flag.
No formatting problems, and nothing the rules object to. Worth remembering what that covers: this reads the file you pasted, not the account or cluster it will be applied to.
No finding matches that filter.
Examples
Real input you can load into the tool above. Each one shows a different thing going wrong, because that is what the tool is for.
An unescaped dot
A dot matches any character, so orders.created also matches ordersXcreated
orders.created ordersXcreated orders-created
Common mistakes
These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.
Leaving a dot unescaped
In a regex a dot matches any character, so orders.created also matches ordersXcreated.
Instead:Escape it as orders\\.created.
Expecting a new topic to be picked up immediately
A pattern subscription re-evaluates on a metadata refresh, controlled by metadata.max.age.ms, which defaults to five minutes.
Instead:Lower it if faster discovery matters, and accept the extra metadata traffic.
Using a pattern that matches internal topics
A broad pattern can match __consumer_offsets or changelog topics, which a consumer should never read.
Instead:Anchor the pattern, and exclude names starting with two underscores.
Kafka matches the whole topic name, and it uses Java's regex
Two facts, and each one causes a different silent failure. A pattern subscription that matches nothing is not an error in Kafka.
It is a full match, not a search
Kafka calls Matcher.matches(), which requires the pattern to match the entire topic name. So a pattern of orders does not subscribe to orders-v2, orders.eu or orders_dlq. Nothing warns you: the consumer joins the group, is assigned no partitions for those topics, polls successfully and returns no records, which looks exactly like an upstream that has gone quiet. This page anchors the pattern at both ends before testing, which is why the answer here can be narrower than you expect.
Java and JavaScript disagree, sometimes silently
Kafka uses java.util.regex and this page runs in a browser, so the engines are not the same. Some Java constructs simply fail to compile here, which is obvious. The dangerous ones compile in both and mean different things: \v is a class of vertical whitespace in Java and exactly one character in JavaScript, [a-z&&[^m]] is a class intersection in Java and two literal ampersands in JavaScript, and \Q ... \E quotes literally in Java and does nothing in JavaScript. Every one of those is reported as a finding rather than quietly assumed equivalent, the same way the JSONPath tester on this site handles dialect differences.
A new topic is picked up on the next metadata refresh
The consumer re-evaluates the pattern when it refreshes metadata, which is metadata.max.age.ms and defaults to five minutes. A topic created now can therefore take that long to be subscribed, and while you are waiting it looks like the pattern is wrong. Lowering it costs more metadata requests against the brokers.
A pattern of .* is rarely what you want
It covers every topic in the cluster including every topic created in future, so an unrelated new topic rebalances your group, and on a large cluster the group can be assigned far more partitions than it can keep up with. Internal topics are excluded separately by exclude.internal.topics, which defaults to true, so __consumer_offsets is not visible to a pattern subscription unless you turn that off.
What this cannot see
It does not know your cluster, so the topic list is the one you type. With ACLs in force a pattern subscription only sees topics the principal is authorized to describe, which means a correct pattern can still match nothing in production and everything in a test cluster. It also cannot run Java, so where the two engines differ this page tells you rather than pretending.
More kafka tools
Kafka Confluent Wire Format Decoder The five junk bytes in front of your payload Kafka Key to Partition Mapper Which partition does this key land on? Kafka Topic Name Validator Legal, risky, or 249 characters too long? Kafka Replication Safety Checker How many brokers can you lose Kafka Producer Config Linter Will it start, and will it lose a record? Kafka Message Payload Decoder The first five bytes are usually not data Kafka Connect Source Connector Generator tasks.max is a ceiling, not a count Kafka Connect Sink Connector Generator A dead letter queue with no context headers is a pile of records Kafka Connect SMT Chain Builder The order is the transforms list Kafka MirrorMaker 2 Config Generator It renames every topic by default Kafka Partition Reassignment Generator The throttle is not optional Strimzi Kafka Resource Generator Without the cluster label, nothing happens Kafka mTLS Config Generator The certificate is the identity Kafka Schema Registry Config Generator The compatibility direction is your deployment order Kafka Exactly-Once Config Generator Half of it is worse than none Kafka Broker and KRaft Config Generator The internal topics that break a one-broker cluster Kafka Quota Generator Byte rates are per broker, not per cluster Kafka Streams Config Generator application.id is four things at once Kafka Connect Worker Config Generator Security three times, or the tasks fail Kafka Retention and Unit Converter log.retention.hours does not take milliseconds Kafka Timestamp Converter Two sentinels and two meanings Kafka .properties to YAML Converter Dotted keys stay flat Kafka Streams Internal Topic Predictor Create them before Streams does Kafka ACL Generator The grant you forgot is on another resource type Kafka Topic Config Generator min.insync.replicas is the one that matters Kafka client.properties Generator The file every CLI tool asks for Kafka Producer Config Generator No password field, on purpose Kafka Consumer Config Generator The commit mode decides the semantics Kafka Disk and Retention Calculator retention.bytes is per partition Kafka Partition Count Calculator The number you can never reduce Kafka Cluster Sizing Calculator The traffic no client metric shows Kafka Consumer Lag Catch-Up Calculator Whether it ever clears, not just when Kafka Producer Batching Calculator linger.ms=0 still batches Kafka Segment and Index Sizing Why retention.ms is a lower bound Kafka Rebalance Duration Estimator What a rolling restart really costs Kafka Cost Estimator Your rates, so nothing goes stale Kafka Config Explorer by Version The answer depends on the release Kafka Default Config Reference What moved under a config you never edited Kafka OAuth Bearer Token Decoder Will Kafka accept it, and can it refresh Kafka Record Header Viewer Headers are a list, not a map Kafka ACL Permission Matrix Viewer DENY beats every ALLOW Kafka Connect Config Validator The mistakes that raise no error Kafka Consumer Group Id Validator Which broker coordinates the group Kafka Partition Assignment Visualizer Leadership is the load, not replicas Kafka Consumer Assignment Visualizer The three assignors disagree Kafka ZooKeeper to KRaft Config Converter The authorizer class nobody changes Kafka Config to Strimzi Half of it belongs elsewhere Kafka Docker Compose Generator (KRaft) Reachable from inside and outside Kafka JAAS Config Decoder The line that stops SASL working Kafka CRC32C Calculator Which CRC, over which bytes Kafka Config Upgrade Checker What breaks when you upgrade Kafka Kafka Config Diff Which change actually changed something Kafka Consumer Config Linter Why the group rebalances, and where the records went Kafka Avro Schema Validator The defaults Avro accepts and rejects Kafka Schema Compatibility Checker What the registry will say, before you ask it Kafka Avro Schema Diff Which direction each change breaks Kafka Compression Comparison Measured on your bytes Kafka Delivery Semantics Exactly-once has a consumer half Kafka ksqlDB Query Builder It looks like SQL and the rules are not Kafka Connect SMT Predicate Tester negate reads backwards Kafka Streams Topology Viewer Count the repartitions Kafka Connect Pipeline Visualizer The order things really run in Kafka Protobuf Binary Decoder Works without the .proto Kafka Protobuf JSON Converter Why your JSON does not round-trip Kafka Protobuf to Avro Schema What does not survive the conversion Kafka Avro Binary Decoder Wrong schema, no error Kafka Avro JSON Converter Why the console producer rejects your line Kafka Avro Sample Data Generator Records that actually serialize Kafka JSON to Avro Schema What JSON cannot tell you Kafka JSON Schema to Avro What does not survive the conversion Kafka SASL JAAS Generator One login module, four syntaxes Kafka CLI Command Builder kcat is librdkafka, not Kafka