🦎 A multi-protocol edge & service proxy. Seamlessly interface web apps, IoT clients, & microservices to Apache Kafka® via declaratively defined, stateless APIs.
Describe the desired outcome from the user's perspective
As a Kafka admin it is hard to understand when Zilla is correctly configured to work with my Kafka cluster and when I have miss configured Zilla, Kafka, or both.
Acceptance criteria
Add positive feedback events when everything is working as expected
Add informative events for when Zilla is actively trying to complete a task and waiting for the correct Kafka state (topics being created, etc)
Add any other relevant status information about Zilla's connection to a TCP client
Additional context
Member of the community troubleshooting would have been able to answer their own question if Zilla had logged a missing topic:
Describe the desired outcome from the user's perspective As a Kafka admin it is hard to understand when Zilla is correctly configured to work with my Kafka cluster and when I have miss configured Zilla, Kafka, or both.
Acceptance criteria
Additional context Member of the community troubleshooting would have been able to answer their own question if Zilla had logged a missing topic: