Kafka Resource

Kafka is an open-source event streaming platform designed to handle massive streams of data in real-time. It offers a distributed architecture, high scalability and fault tolerance, allowing large volumes of data to be processed and transmitted efficiently and reliably. In Kafka, data is organized into topics, which are divided into partitions distributed among Kafka brokers. Producers publish logs to topics, and consumers can subscribe to receive these logs in real time. This makes Kafka ideal for use cases such as real-time event processing, batch data ingestion, asynchronous messaging, systems integration, and data pipeline. With its high throughput and low latency, Kafka has been widely adopted by enterprises to build scalable and distributed data architectures, enabling real-time analytics, streaming processing, and building high-performance applications.

How to monitor Kafka on One Platform

1 – In the side menu, click on Services Hub



2 – In the Queue category, click on the Kafka card



3 – You will be directed to the Kafka configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING 


Kafka is an open-source event streaming platform designed to handle massive streams of data in real-time. It offers a distributed architecture, high scalability and fault tolerance, allowing large volumes of data to be processed and transmitted efficiently and reliably. In Kafka, data is organized into topics, which are divided into partitions distributed among Kafka brokers. Producers publish logs to topics, and consumers can subscribe to receive these logs in real time. This makes Kafka ideal for use cases such as real-time event processing, batch data ingestion, asynchronous messaging, systems integration, and data pipeline. With its high throughput and low latency, Kafka has been widely adopted by enterprises to build scalable and distributed data architectures, enabling real-time analytics, streaming processing, and building high-performance applications.

How to monitor Kafka on One Platform

1 – In the side menu, click on Services Hub



2 – In the Queue category, click on the Kafka card



3 – You will be directed to the Kafka configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING