The Ultimate Engineering Toolkit for Apache Kafka®
Search…
kPow User Guide
About
Introduction
Our Team
Releases
Trials and Licenses
Support
Data Collection
Installation
Quick Start
System Requirements
Deployment Notes
Minimum ACL Permissions
Application Logs
OpenShift
AWS Marketplace
Troubleshooting
Configuration
Environment Variable Glossary
Kafka Cluster
Schema Registry
Kafka Connect
Multi-Cluster Management
Azure Event Hubs
Confluent Cloud
Redpanda
User Authentication
Overview
LdapLoginModule
PropertyFileLoginModule
JDBCLoginModule
OpenID/OAuth 2.0
SAML
User Authorization
Overview
Simple Access Control
Role Based Access Control
Multi-Tenancy
Administration
Features
Kafka Streams
Data Governance (Audit Log)
Data Policies
HTTPS Connections
Live Mode
Data Inspect
Data Produce
Prometheus Integration
Slack Integration
Kafka Management
Topics
Groups
Brokers
ACLs
Connect
Schema Registry
Powered By GitBook
Azure Event Hubs
Use kPow with your Azure Event Hubs namespace.

Prerequisites

kPow can connect to your Azure Event Hubs namespace(s) if you have enabled Kafka Surface. You can read about using Event Hubs with Kafka here.
You can verify that Kafka Surface has been enabled, by navigating to your Event Hubs namespace overview inside the Microsoft Azure portal:
Verifying Kafka Surface is enabled

Configuration

Once you have verified Kafka Surface is enabled, visit the Security and authentication section of Azure's documentation to find Kafka configuration properties for each type of authentication mechanism.
For example, if you were to use Shared Access Signature (SAS) connection details, the environment variables passed to kPow would look like:
1
BOOTSTRAP=NAMESPACENAME.servicebus.windows.net:9093
2
SECURITY_PROTOCOL=SASL_SSL
3
SASL_MECHANISM=PLAIN
4
SASL_JAAS_CONFIG=sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username="$ConnectionString" password="{YOUR.EVENTHUBS.CONNECTION.STRING}";
5
CLUSTER_ID=azure-event-hubs
6
AZURE_EVENT_HUBS=true
Copied!
Note: an extra environment variable CLUSTER_ID is required, as Azure event hubs does not provide a cluster ID when making an admin client request. The CLUSTER_ID must be unique across all clusters defined in kPow, and can be any unique identifier (eg, the namespace name of your event hub)
The AZURE_EVENT_HUBS environment variable must be set to true as Event Hubs does not support the topic configuration of retention.ms set to -1 (which is set by kPow's audit log + Kafka Streams internal topics). Topics that normally have infinite retention will have a 7 day retention set in Event Hubs.

Event Hubs limitations

The vast majority of kPow's features work with Azure Event Hubs, with the exception of:
    Broker disk information/metrics - as the admin client request does not return any log details
    Broker configuration - as the admin client request does not return any broker configuration details
Configuration - Previous
Multi-Cluster Management
Next - Configuration
Confluent Cloud
Last modified 6mo ago
Copy link
Contents
Prerequisites
Configuration
Event Hubs limitations