2026.11.3 — 2026-11-02

Breaking

• Report NOT_AUTHORIZED when an ACL or permission refuses a node's call (b40af8d6)

  A node whose last call an ACL or a permission refused now reports lastErrorKind: NOT_AUTHORIZED on the cluster, topology and node responses, where it reported BAD_RESPONSE. The field's description says what each kind means.

Fixed

• Report NOT_AUTHORIZED when an ACL or permission refuses a node's call (b40af8d6)

  A node whose last call an ACL or a permission refused now reports lastErrorKind: NOT_AUTHORIZED on the cluster, topology and node responses, where it reported BAD_RESPONSE. The field's description says what each kind means.

• Drop Artemis wording from copy every broker system sees (7984bdc4)

  The default email subject prefix, the skipped-node summary, the API token pattern hint and the slow-consumer capability note named Artemis on Kafka and RabbitMQ clusters. They are neutral now, and the capability note points at the backlog and lag metrics a Kafka or RabbitMQ rule can use.

• Read an address that answers as something else as a wrong address (ebd2acdb)

• Name Kafka and RabbitMQ in broker errors instead of Artemis (acc91027)

  A Kafka or RabbitMQ cluster that failed read as an Artemis one: "This Artemis version is not supported" for a Kafka request an old broker cannot answer (The node does not support LIST_TRANSACTIONS), "There is no Artemis broker at this agent" for an answer Rahdar did not map, and "unexpected response" for an ACL or permission refusal.

  • Broker problems carry the system they are of, and the console words each kind for it (Kafka, RabbitMQ, or the generic broker when none is named).
  • A refused account (a Kafka ACL, a RabbitMQ permission) is its own kind, NOT_AUTHORIZED, with the ACL named as the next step.
  • A Kafka request the brokers' release is too old for is a 409 feature gap that says which request, not an unsupported cluster.
  • The Kafka and RabbitMQ native error text reaches the operator beside the cause.