Skip to content

Commit

Permalink
docs update
Browse files Browse the repository at this point in the history
  • Loading branch information
guilhemmarchand committed Dec 2, 2018
1 parent b33ce20 commit cb82fee
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 9 deletions.
Binary file modified docs/img/itsi_dep.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
24 changes: 15 additions & 9 deletions docs/service_creation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,23 +3,29 @@ Services creation

**The ITSI module for Telegraf Kafka smart monitoring provides builtin services templates, relying on several base KPIs retrieving data from the metric store.**

* **Zookeeper monitoring**: provides insight monitoring for Zookeeper servers
* **Zookeeper monitoring**

* **Kafka brokers monitoring**: provides insight monitoring for the Kafka broker infrastructure
* **Kafka brokers monitoring**

* **Kafka LinkedIn monitor**: provides insight monitoring for the LinkedIn Kafka monitor, end to end monitoring for your Kafka deployment
* **Kafka LinkedIn monitor**

* **Kafka topic monitoring**: provides insight momitoring for one or more Kafka topics
* **Kafka topic monitoring**

* **Kafka connect monitoring**: provides insight monitoring for the Kafka connect infrastructure
* **Kafka connect monitoring**

* **Kafka sink task monitoring**: provides insight monitoring for Kafka connect sink tasks
* **Kafka sink task monitoring**

* **Kafka source task monitoring**: provides insight monitoring for Kafka connect source tasks
* **Kafka source task monitoring**

**As a general practice, if you first goal is designing the IT infrastructure in ITSI, a good generic recommendation is to create a main service container for your Kafka infrastructure.**
* **Confluent schema-registry monitoring**

**As such, every service that will be designed will be linked to the main service. (the main service depends on them)**
* **Confluent Confluent ksql-server monitoring**

* **Confluent kafka-rest monitoring**

As a general practice, if you first goal is designing the IT infrastructure in ITSI, a good generic recommendation is to create a main service container for your Kafka infrastructure.

As such, every service that will be designed will be linked to the main service. (the main service depends on them)

.. image:: img/itsi_dep.png
:alt: itsi_dep.png
Expand Down

0 comments on commit cb82fee

Please sign in to comment.