View all the existing topics of an environment. It is also possible to search based on search filters. My Producer topics, my consumer topics part of the dashboard.
Topic configuration details like partitions, replication factor and retention period can be viewed. and edited
Producers and Consumers, with IP address or SSL DN names, consumer groups are detailed in this view. Prefixed, Transactional, Literal.
Topic contents can be viewed from a selected list of offsets. Ex : Last 20 offsets, or 50 offsets etc.
Avro schema registered in Schema registry of every environment can be viewed.
Manage kafka connectors with self service. Ability to add, delete, edit, get and promote kafka connectors.
Ability for each tenant to manage their environment and topics with their own teams in isolation.
View consumer offsets and lag of your topic consumer groups
Ability to configure roles and assign permissions to roles. Gives the flexibility to adapt according to your organization needs.
Every request and its approval is audited and is visible to users. Request can be Topic/Acl/Schema/NewUser etc..
New Users and Teams can be added/viewed by superusers. Users can have USER/ADMIN/SUPERUSER or any configurable roles
Can be connected to an Rdbms or File system as a metastore to store all the metadata.
By introducing ownership on Topics, Acls and Avro schemas
New topics can be requested to be created, and on approval, topics are directly created on the cluster
New subscriptions on topics can be requested to be created, and on approval, subscriptions are directly added to topics on the cluster. (LITERAL/PREFIXED and Transactional ID)
New Avro schemas can be requested to be created, and on approval, schemas are directly created on the schema registry server
New users can register, and on approval by superusers, users are created. Users have different roles. New teams can be created by superuser. Teams contain a bunch of users. Teams own topics, acls, schemas.
Clusters and Environments can be easily added/updated to connect to Kafka clusters
Kafkawize is based on 4-eye principle. Every request is approved by a different user, making sure it is reviewed.
Providing end-to-end automation
Topics from lower environments can be requested to be promoted to higher envs. This way it restricts users to create topics in adhoc way and at the same time maintains data integrity.
When a topic is no more needed,it is best to get it deleted. So we save on the partitions loaded by the cluster. This feature makes sure a topic can only be deleted when there are no subscriptions for the topic.
It is possible to delete particular Producer or Consumer subscriptions of a topic with this feature. This deletion request can be triggered by that Acl owner teams. No other teams can request for other’s acl deletion.
- With SSO - OAuth2 enabled, users do not have to enter credentials again.
- Users can be authenticated against Active Directory/Ldap while users login to Kafkawize.
If you do not want to create/use a different password for Kafkawize users, rather authenticate from your organization ActiveDirectory/Ldap server. It is easy to integrate.
Kafkawize can connect to Kafka clusters over PLAINTEXT protocol. This is not very secure.
Kafkawize can connect to Kafka clusters over SSL protocol. This is the most secure option.
Kafka-Jaas configuration has to be setup on the Kafka cluster. This is can be done in PLAIN or with Kerberos auth mode
Kafkawize can be well integrated into your organization applications, by our white labelling support, for example on logo, colors, etc.
Customers receive support from Kafkawize, if any issues in installation or issues found.
Customers can request for minor customizations of UserInterface.
Our customers receive free updates from Kafkawize.
A situation where Kafka cluster already exists and would like to adapt Kafkawize in your organization, all the topics and acls need to have their teams/owners. It is possible with Synchronization of Topics or Acls. Also in case of cluster had any issues, and lost topics and acls, it is possible to restore the whole config.
For every request and approval, through out the Kafkawize application, emails are sent out to approvers, and after approvals, notify the requesters. When a new user is added, or password changes, etc, notifications are enabled.
All the requests from users are audited and can be viewed. Every request and its approval is audited and is visible to users of all teams. Request can be Topic/Acl/Schema/NewUser etc. This helps in efficient tracking of any request.
Dashboard displays different statistics like number of topics owned by teams, status of clusters Dev, Tst, Acc, Prd, status of clusterapi, pendng requests to be approved or declined, and number of configured clusters.
With full self service enabled, its a ZERO risk of manual errors, saving costs on time and effort.Get Started Now with Demo!
Reliable, scalable and easy to deploy
Both the UserInterface and Cluster apis are built with Spring boot frameworks.
Spring security enables tight security with basic authentication or Ldap authentication.
Front end is built with Angular framework, making it more easy to scale, and add components on top.
Metastore can be an Rdbms or File system. Teams, users and their ownership on topics, acls and schemas info is stored in metastore