Produce and consume messages

Send test messages, replay real ones, and read topics live or up to their end, with server-side search and masking of personal data.

Produce a message

  1. In Topics, open the action menu of a topic and choose Produce.
  2. Fill in the headers (optional), the key and the value. Set the acknowledgment mode if needed.
  3. If the topic uses Schema Registry, pick the key and value schemas: KCM serializes Avro and JSON Schema messages and validates them against the schema.
  4. Click Produce. A notification gives the partition and offset. The button is disabled while sending, so a double click never sends twice.
Produce message dialog with headers, key and value
Produce with headers, a key and a schema-aware value.

Producing needs WRITE on the topic, through a cluster EDITOR or ADMIN role or a topic grant. Every message produced from KCM is recorded in the audit trail, without its content.

Templates and history

Template picker in the produce dialog
Pick a template of this topic or from your whole library.

Bulk produce

The bulk producer sends many messages at once, each with its own key and headers, typed in the editor, built from templates, or exported from the consumer page. A results window lists each message sent.

Consume messages

Open Data Consumer (or Consume from a topic), pick the cluster and the topic, choose where to start, then Start. Several consumer tabs can stay open side by side, each with its own settings.

Data Consumer criteria: topic, partitions and start position
Choose the topic, the partitions and where to start.

Where to start

Start fromReads
LatestOnly new messages.
Last N messagesThe last N messages (10 to 10,000 in the console), spread over the non-empty partitions, then new ones.
EarliestFrom the beginning of each partition.
Date timeFrom a date, optionally up to an end date. A partition with no message after the date starts at its end.
By offsetFrom a start offset per partition, optionally up to an end offset.

Every mode works on all partitions or on the ones you select. Read committed hides messages of aborted transactions.

Live tail, pause, resume and stop

KCM never moves your consumer offsets

The consumer page never commits offsets. Reads from a date, an offset or the last N messages leave no consumer group on the brokers; other reads use a temporary group with the KCM prefix (KCM_ by default), deleted when the session ends. Leftover empty temporary groups are cleaned up every hour.

Filters run on the server, on every message read, before anything reaches the browser. All filters must match (up to 20 per session).

Data Consumer filters on key, value and headers
Filters on keys, values, headers and JSON fields run on the server.

Masking comes first

When a topic has masked fields (see Classification and masking), KCM masks each message before applying the filters, so a filter can never reveal a masked value by matching it. Messages that cannot be decoded are not sent at all for such topics.

Work with the results

Table of consumed messages
Consumed messages, with export and replay actions.

Permissions and limits