Kafka Metadata Tags
AxonOps allows metadata tags to be attached to Kafka objects. A tag is a key/value label recorded within AxonOps and associated with a specific object, independent of any configuration held by the Kafka cluster itself.
Tags are supported for the following object types:
- Topics
- Consumer groups
- Access-control lists (ACLs)
- Kafka Connect connectors
- Schema Registry entries
Where tags are recorded
Section titled “Where tags are recorded”Metadata tags are AxonOps-side metadata. They are stored and managed by AxonOps and are not Kafka broker or topic configuration; setting or changing a tag does not write anything to the Kafka cluster. A tag exists only in AxonOps and has no effect on broker behaviour, topic configuration, or client access.
Tags are edited from a dedicated metadata tags page in axon-dash, the AxonOps web interface, under its settings. For topics, tags can additionally be set at creation time on the create-topic form. A saved tag appears on the metadata tags page and is reflected in the topic classification catalogue on the Data Classification page.
Default topic tags
Section titled “Default topic tags”Two tags are provided by default for topics: data-classification and owner. Operators can also add arbitrary free-form key/value tags to a topic beyond these two.
The data-classification tag takes one of a fixed set of values:
- Public
- PII (personally identifiable information)
- PCI (payment card data)
- Financial
The owner tag records the accountable party for a topic as free text.
Owner enforcement for regulated classes
Section titled “Owner enforcement for regulated classes”When a topic is created through the AxonOps create-topic form, an owner value is required if the data-classification tag is set to PII, PCI, or Financial. The form does not enforce an owner for topics classified as Public or for topics left unclassified.
This validation applies at creation time, through the create-topic form. Tags on an existing object are edited from the metadata tags page, which does not re-impose the owner requirement; removing the owner from a regulated topic there is one cause of a regulated topic without a recorded owner. A topic created outside AxonOps, through kafka-topics.sh, the Kafka Admin API, or automatic topic creation (when the broker’s auto.create.topics.enable is set), never passes through the form and can carry a regulated classification with no owner, or no classification at all.
Related pages
Section titled “Related pages”- Kafka Compliance: Data Classification reports the topic classification catalogue and the regulated topics that have no recorded owner, built from the
data-classificationandownertags described here. - Kafka Compliance Overview surfaces the regulated-topics-without-owner count as one of its indicator tiles.