There’s a new post on the Confluent blog. Here’s a snippet from it:
The next time you hit a snag in your Kafka cluster, take some time to diagnose and debug. Before committing to making changes to your applications, it’s important to understand what’s causing your problem and uncover the underlying ailment.
Head over to the blog to read the full article