Installation Guide
Pulse 4.1.x
Overview
Prerequisites
Installation
Advanced Installation
Admin UI (K8S only)
Pulse Administration
Upgrade
Advanced Feature Integrations
Developer Tools
Troubleshooting
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Configure Pulse to Monitor Standalone Kafka 3 with Kerberos
Summarize Page
Copy Markdown
Open in ChatGPT
Open in Claude
Connect to Cursor
Connect to VS Code
This page describes about configuring Pulse to monitor standalone Kafka 3 with Kerberos.
- On a Pulse node, run
accelo config cluster. - Select
Stand-Alonedeployment during deployment type.

- Select
Kafka3Standalone component.

- Enter Cluster Name.

- Enter
Kafkabootstrap server’s URI.

- Select Kerberos as the security type.

- Select
TLSis enabled or not.

- Enter
Kerberos Authentication Realm.

- Enter
Kerberos keytab username.

- Enter
Principalfor kafka client.

- Enter full path to the
Client Keytabfile.

- Enter full path to the
krb5.conffile.

If the above configurations are correct, the CLI will automatically fetch the list of brokers.
- Verify the list and select
yto proceed.
- Verify the list and select

- Select Metadata Manager → Zookeeper / KRaft.

- Enter the URI’s for
MetaData Manager.

- Enter
Kafka Connecthostname and port.

- Enter
Cruise Controlhostname and port.

- Enter
Schema Registryhostname and port.

- Enter the
ssh userdetails.

- Enter all the required JMX ports and LogSearch configurations.

Additional Configuration
- Update Kafka Connector Config
Add the following in:
Bash
xxxxxxxxxx$ACCELDATA_HOME/config/acceldata.confBash
xxxxxxxxxxkafka3.connectors { saslMechanism = "GSSAPI"}- Configure Log Locations
Create:
Bash
xxxxxxxxxx$ACCELDATA_HOME/work/<cluster_name>/override.ymlAdd:
Bash
xxxxxxxxxxlog_locations: kafka3_connect: - path: /path_to/connect.log type: DEFAULT kafka3_connect_err: - path: /path_to/kafka-connect.err type: KAFKA_ERR kafka3_controller: - path: /path_to/controller.log type: DEFAULT kafka3_cruise_control: - path: /path_to/kafkacruisecontrol.log type: DEFAULT kafka3_cruise_control_err: - path: /path_to/cruise-control.err type: KAFKA_ERR kafka3_log_cleaner: - path: /path_to/log-cleaner.log type: DEFAULT kafka3_server: - path: /path_to/server.log type: DEFAULT kafka3_server_gc: - path: /path_to/kafkaServer-gc.log type: DEFAULT kafka3_state_change: - path: /path_to/state-change.log type: DEFAULT kraftbroker_err: - path: /path_to/kraft-broker.err type: DEFAULT kraftcontroller_err: - path: /path_to/kraft-controller.err type: DEFAULT registry_err: - path: /path_to/registry.err type: REGISTRY registry_server: - path: /path_to/registry.log type: REGISTRY- Apply Configuration to Update Vars.yml.
Bash
xxxxxxxxxxaccelo reconfig clusterKafka Data in Pulse
After the configuration, you can see the Kafka data in Pulse.
Kafka Dashboard

Kafka Nodes

Kafka Logs

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message