To carry out this step, the person responsible must know how a Kafka cluster works.
The monitoring configuration is done when an External Dependencies (Add-On) is added to the application.
Four ways to check the cluster.
1 - Connection without authentication and simple verification of a specific topic for 1P: HOST:PORT/TOPIC
2 - Connection without authentication and simple verification of a specific topic for 1P, but with a list of brokers: [HOST1:PORT,HOST2:PORT]/TOPIC
Or
HOST1:PORT,HOST2:PORT/TOPIC
3 - Connection without authentication and verification of the delay size in the messages consumption of a topic (Production topic), from the point of view of a consumer group:
[HOST:PORT]/TOPIC/CONSUMER-GROUP/LAG-TOLERANCE
4 - Connection with SASL authentication and simple verification (or not) USER:PASSWORD:MECHANISM:TLS:SASL@[HOST1:PORT,HOST2:PORT]/TOPIC or USER:PASSWORD:MECHANISM:TLS:SASL@[HOST1:PORT,HOST2:PORT]/TOPIC/CONSUMER-GROUP/LAG-TOLERANCE
Example of verification string from example 4: kafka:{{.kafka_password}}:SCRAM-SHA-512:true:true@[b-2.kafka-production.amazonaws.com:9096,b-1.kafka-production.amazonaws.com:9096,b-3.kafka-production.amazonaws.com:9096]/eventos/consumidor-de-eventos/200
For further questions, contact our technical support via chat on 1P or on the website.