Skip to main content

What does Atlan crawl from Confluent Kafka?

Atlan crawls and maps the following assets and properties from Confluent Kafka.

Once you've crawled Confluent Kafka, you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets:

  • Topics - Message count, size (MB), partition count, and cleanup policy filters
  • Consumer groups - Member count and topic name filters

Topics

Atlan maps topics from Confluent Kafka to its KafkaTopic asset type.

Source propertyAtlan property
Topicname
PartitionCountkafkaTopicPartitionsCount
ReplicationFactorkafkaTopicReplicationFactor
segment.bytekafkaTopicSegmentBytes
compression.typekafkaTopicCompressionType
cleanup.policykafkaLogTopicCleanupPolicy
isInternalkafkaTopicIsInternal
sizeInByteskafkaTopicSizeInBytes
recordCountkafkaTopicRecordCount
retention.mskafkaTopicRetentionTimeInMs
danger

Retrieving sizeInBytes Confluent Kafka to be set up with a Cloud API key and secret. If the Cloud API key is not configured or the API key and Secret are not set, sizeInBytes will be set to 0.

Consumer groups

Atlan maps consumer groups from Confluent Kafka to its KafkaConsumerGroup asset type.

Did you know?

Consumer groups are most likely to show up only in streaming scenarios. This is because if a topic is not being consumed actively, Confluent Kafka will purge the consumer group. So, if a consumer group is inactive while the workflow runs in Atlan, it will not be cataloged as an asset.

Source propertyAtlan property
GROUPname
memberCountkafkaConsumerGroupMemberCount
ReplicationFactorkafkaTopicReplicationFactor
topic_nameskafkaTopicNames
TOPICkafkaConsumerGroupTopicConsumptionProperties.topicName
PARTITIONkafkaConsumerGroupTopicConsumptionProperties.topicPartition
LAGkafkaConsumerGroupTopicConsumptionProperties.topicLag
CURRENT-OFFSETkafkaConsumerGroupTopicConsumptionProperties.topicCurrentOffset