🎉 First release HZN Queue Console 1.0 is out. Get 30% off with code FIRSTRELEASE30— limited number of customersSee pricing →
Message Filtering

Message Filtering

HZN Queue Console lets you search and filter messages within a queue without consuming them. Filters are applied on top of the fetched message set and update results as you type.

Opening the Filter Bar

Select a queue to open the message browser, then click the Filter bar above the message table (or press / to focus it).

Beside the filter bar is an In field selector. It decides where the term is looked for, and lists the same things the column picker does:

  • All fields — the default. The payload, every one of the message’s own fields, and every header. A match anywhere is enough
  • Payload (raw) — the message body as text, whatever its content type: JSON, XML, plain text, or binary shown as hex
  • Standard — one of the message’s own fields: routing key, exchange, content type, correlation ID, reply-to, JMS type, message ID
  • Payload — a single field within the payload, nested paths included. Choosing items.productName searches that field and nothing else
  • Headers — one header, by key

Matching is case-insensitive and partial throughout: invoice finds invoice_id.

Narrowing the field is worth doing when a term is common. Searching everything for dlq finds it in routing keys, payloads and headers alike; searching Routing Key for it finds only the messages routed there.

Redelivered and Timestamp are columns but not filter fields — one is a flag and the other a number, and neither answers a text search.

Where matches are shown

A match is marked wherever it can be seen: in the cell that holds it, in the payload of a stream entry, and in the tooltip over a value the cell had no room for.

Where a cell shows {…} or [3] rather than the value itself, the whole token is marked instead — the row is telling you it matched, and the tooltip shows where.

Combining Filters

All active filters are applied together (AND logic). A message must match every active filter to appear in the results. Clear individual filters by clicking the × next to each field, or click Clear all to reset.

Schema-Aware Filtering

If you have an AsyncAPI schema (see Schema Validation) loaded for the queue’s message type, the filter bar gains extra typed fields derived from the schema — one input per top-level property. This makes it easy to filter by domain-specific fields like customerId, orderId, or status without knowing the exact JSON path.

Table View Filters

In Table View mode, each column header has an inline filter input. These work the same as the filter bar but are scoped to that column’s value.