.png)
KafkaFix is designed to simple and lightweight local Kafka development tool with support for graphical UI for monitoring JMX attributes with Prometheus.
Kafkafix aims to get rid of all configurations on the user's end to simplify the process and offer better user experience. Users simply have to fire up the application with their docker compose file. Then, everything is good to go.
Users are able to fully manage their local Kafka instance and perform any operations, such as, create topics, start consumers and producers, visualize streams of data, manage errors.
Just visit https://wwww.kafkafix.com and download and install.
- Start all containers by selecting your docker-compose.yml file.
- Provide a local port number and click Connect
- Click Disconnect button and all containers will be stopped.
- To visualize metrics, click the side panel and then click Metrics
- Here you will have an options to see all possible JMX metrics
- Click on any of the metrics and you will be able to see visual representation of data for that metric.
- All failures incurred by Kafka will be saved locally.
- Click on the side panel for full history or error logs or click on top right notification panel for most recent error logs.
- To visualize all streams of data consumed by the conusmer go to right panel and click on the Visualize Streams button.
- All data will be update in real time.
- To create a topic, click on the Create Topic button
- Pass in the topic name and the Number of Partitions you like for the topic to have.
- To start a producer, click on the Start Producer button
- Provide name of the topic you would like producer to
- Kafkafix will start producing to that topic
- To start a consumer, click on the Start Consumer button
- Provide a topic name and a group id.
- Once it's created, consumer will start consuming messages for the specified topic.
- Simply click on the Delete button next to the topic name.
- Click on Create a Paritition button.
- Then pass in a number of partitions to be added for the topic.
- Before opening a PR for major additions or changes, please test on your local development. This way, it will save overall time spent and allow for faster implementation by maintainers.
- Conside whether your changes are useful for all users.
- Avoid breaking changes unless there is an upcoming major release, which are infrequent. We encourage people to care a lot about backwards compatibility.