Management

• SSO with LDAP.

• Alerting by creating alert rules that listen to specific thresholds and notifying you by email, slack or even by creating issues (gitlab, github, jira ...).

• Enhancing permissions to be even more granular and easier to setup.

• Currently access and refresh tokens are stored in a serveronly cookie, but only for the tokens managed by Blazing KRaft, when using an OIDC Provider I usedthis librarythat seems to be handling them in local and session storage which is a big no no. Therefore I'll either look for another way to store them securily on the browser, or I'll write my own client library that would only handle my specific use cases and may not be 100% RFC compliable.

• Adding DEBUG audit level to be able to audit, in addition to all mutation actions, all get actions performed by your users.

• Adding a VEBOSE audit sublevel to give to possibility to store more information about the performed action, ex: Storing the record key/value/headers when a Produce action is performed... It will be disabled by default and you should opt-in for this behavior.

• Adding Data Masking for configuration values to be able to mask the sensitive configuration secrets.

• Optimizing the Groups/Users management.

Clusters

• Advanced Monitoring using the usefull JMX metrics exported by the brokers and storing them in either a timeseries database or even in an SQL database but with a timeseries compliant manner.

• Adding the generic deserializer to the consumer (Even for Schema Registry Deserializers by utilizing the magic byte) that will automatically detect content types and deserialize accordingly.

• Adding a drawer or modal in the Consumer UI that enables you to produce a record or even reproduce a record that you've just consumed.

• Adding the possiblity to generate random data in the Producer even when selecting schema registry serializers.

• Exporting consumed records as CSV/JSON/Avro...

• Giving the ability to enforce content schemas when producing and consuming records on the topic level (schema per topic(s)).

• Integrating with Upstash, Confluent, Aiven APIs to give you full control over your resources even when cloud providers restrict some admin client's functionalities.

• Persisting the producer/consumer settings (default serializer, initial filters ...) in the browser's local storage, so you don't have to reconfigure them every time you re-open the page.

• Adding an export/import feature to enable sharing your configurations with your team.

• Managing the kafka streams topologies in a feature rich UI.

• Optimizing performance and polishing the UI of all Cluster features.

Kafka Connects

• For advanced monitoring, same goes for Kafka Connect as for Kafka Clusters.

• List active topics in the connector details page.

• Enhance connector' and task' error handling.

Schema Registries

• For Schema Registy advanced monitoring, the server doesn't export userfull JMX metrics that are interresting to track in timeseries.

• Adding possiblity to normalize a schema when creating a subject or subject version.

• Optimize schema definition and content validation.

KsqlDBs

• For advanced monitoring, same goes for KsqlDb as for Kafka Clusters.

• Optimize query execution and streaming, and statement execution.

Playground

• Adding more interresting conversions (AVRO to JSON to PROTOBUF to OPENAPI conversion)

• Adding possiblity to beautify all schema definition types and all content types.

Feedback

This list is not sorted by priority.

Some of these features are not going to be implemented in the near future, I just wanted to list everything that for Me is going to make Blazing KRaft even more Blazingly AWESOME.

If you have any ideas for new features, please submit them in this repository (opens in a new tab) and I'll try to get back to you as soon as possible.