Skip to main content

What does Atlan crawl from Microsoft Azure Event Hubs?

Atlan crawls and maps the following assets and properties from Microsoft Azure Event Hubs.

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

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

Event hubs

Atlan maps event hubs from Microsoft Azure Event Hubs to its AzureEventHub asset type.

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

Consumer groups

Atlan maps consumer groups from Microsoft Azure Event Hubs to either of the following asset types:

  • KafkaConsumerGroup - managed via Kafka clients.
  • AzureEventHubConsumerGroup - managed via Azure portal, SDK, or Azure Resource Manager templates.
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, Microsoft Azure Event Hubs 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