Kafka Streams

Conduktor allows you to monitor your Kafka Streams applications and do the links with the existing topics, consumer groups etc. that the Kafka Streams application is using.

Work In Progress

How to import a Topology inside Conduktor, and why?

Kafka Streams applications are outside of the scope of Kafka itself, they can be running anywhere. They generally work with many topics (in/out/internal/intermediates) and can be reset when you want to start it fresh again.

Conduktor can help you monitoring these applications, and the topics being used.

To do so, go to the Kafka Streams menu and click on IMPORT TOPOLOGY, then:

  • Specify the application.id of your application

  • Specify the topology

    • Static: paste your topology directly inside Conduktor

    • by URL: paste the endpoint of your application exposing its topology.

      • Conduktor will automatically fetch it regularly, adapt the metrics accordingly, and warn you if it's down

Here is an example importing a Kafka Streams application using the application.id myapplicationid and exposing a endpoint /topology:

Conduktor will then monitor the endpoint and display a summary (topics in and out) in the main listing:

If the application is down, the topology disappears and it becomes redish, time to call the developers!

How to reset a Kafka Streams Application?

Conduktor can help you in two ways:

  • Do it manually by specifying all of topics in/out/internals/intermediate. It's not super practical.

  • Do it with all topics already set because you imported the Topology within Conduktor already

Manual (specify everything) or a registered application in Conduktor

A wizard will then helps you by explaining the steps:

If you're doing a reset of a registered Kafka Streams application within Conduktor, you can just hit Next until the end, everything is setup automatically! 🤩