Architecture


PATROL for Apache Kafka enables you to monitor the Apache Kafka broker and the topic attributes. A typical architecture for PATROL for Apache Kafka is as follows:

 

Kafka KM architecture.png

Collector details

The following table lists the different PATROL for Apache Kafka collectors and explains how they work:

Collectors 
(Collection interval)

Description

AutoDiscovery
(23 hours 59 minutes 59 seconds)

This collector parameter is responsible for a force discovery of the Kafka environment in the stipulated period of time.

This attribute is displayed on the console as DiscoveryTime

SetDataToPatrol
(1 seconds)

This attribute runs every second, to check if any data is received from JAVA. If yes, the parameter reads the data and sends it to PATROL Agent.

This attribute is not displayed on the console.

ChannelListener
(2 seconds)

The ChannelListener attribute runs the listener method every two seconds to check the following:

  • If the Java collection should start for a new environment
  • If the Java collection should restart for a specific environment

This attribute updates the MonitoringStatus parameter, if the Java collection fails to start for some reason.

This attribute is not displayed on the console.

ConfigurationManager
(15 seconds)

This attribute runs every 15 seconds to check if the Kafka configurations are changed in the pconfig variables. This attribute is responsible for adding a new environment, editing a current environment and deleting an environment after the changes are done to the pconfig variables.

This attribute is not displayed on the console. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*