THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Connect framework provides good metrics for monitoring behavior. Currently, we have a metric on the Worker to measure number of tasks: .
It is useful in many applications to measure the number of tasks on a Connector. For example, an administrator may wonder the average number of tasks per connector, which types of connectors create the most tasks, if some connectors are outliers (creating too many or too few tasks). The current metric providing tasks per Worker is useful in its own right, but does not address any of these needs.
Further, it is useful to know the breakdown of how many tasks on a connector are running, paused, or failed.
Public Interfaces
We propose adding the new metric "connector-task-count" following new metrics on the existing group name "connector-metrics" in the ConnectMetricsRegistry.
| MBean | Metric/Attribute Name | Description |
|---|---|---|
kafka.connect:type=connector-metrics,connector=([-.\w]+) | connector-total-task-count | The number of tasks of the connector. |
Proposed Changes
kafka.connect:type=connector-metrics,connector=([-.\w]+) | connector-running-task-count | The number of running tasks of the connector. |
kafka.connect:type=connector-metrics,connector=([-.\w]+) | connector-paused-task-count | The number of paused tasks of the connector. |
kafka.connect:type=connector-metrics,connector=([-.\w]+) | connector-failed-task-count | The number of failed tasks of the connector. |
Proposed Changes
The above metrics will be added. These A new Connector level metric will be added, "connector-task-count". This metric will be calculated from the `Herder::connectorStatus` method. In order to enable this change, the `WorkerConnector` will be constructed with a `Herder` to have access to the task statuses.
...
This KIP simply adds a new metric.
Rejected Alternatives
...
Excluding the "connector-" prefix
"connector-task-count" prefix keeps naming consistent with the existing names "connector-version", "connector-type", and "connector-status". Further, while not strictly necessary, it does disambiguate from the Worker's "task-count" metric name.
...