openstack
/
monasca-agent
Code Issues Proposed changes

Invalid kafka_consumer documentation 

kafka_consumer is able to figure
out partitions on its own, there is
no need to specify them here.

Change-Id: I9f97d95bf49b7b89a4eccfa119e07cb30e4f37b1
This commit is contained in:
Tomasz Trębski 2016-09-01 10:11:18 +02:00
parent 1ded4ca81a
commit 1a25c633b8
2 changed files with 12 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
conf.d/kafka_consumer.yaml.example
View File

@ -4,8 +4,6 @@ init_config:
instances: instances:
# - kafka_connect_str: localhost:19092 # - kafka_connect_str: localhost:19092
# zk_connect_str: localhost:2181
# zk_prefix: /0.8
# It is possible to get the lag for each partition, the default is to sum lag for all partitions # It is possible to get the lag for each partition, the default is to sum lag for all partitions
# per_partition: False # per_partition: False
# Full includes additional metrics with actual offsets per partition, can't be set if per_partition is False # Full includes additional metrics with actual offsets per partition, can't be set if per_partition is False

26
docs/Plugins.md
View File

@ -941,23 +941,21 @@ This section describes the Kafka check that can be performed by the Agent. The
Sample config: Sample config:
``` ```yml
init_config: init_config:
instances: instances:
- consumer_groups: - built_by: Kafka
'1_alarm-state-transitions': consumer_groups:
'alarm-state-transitions': ['3', '2', '1', '0'] 1_metrics:
'1_metrics': metrics: []
'metrics': &id001 ['3', '2', '1', '0'] thresh-event:
'test': events: []
'healthcheck': ['1', '0'] thresh-metric:
'thresh-event': metrics: []
'events': ['3', '2', '1', '0'] kafka_connect_str: 192.168.10.6:9092
'thresh-metric': name: 192.168.10.6:9092
'metrics': *id001 per_partition: false
kafka_connect_str: localhost:9092
zk_connect_str: localhost:2181
``` ```
The Kafka checks return the following metrics: The Kafka checks return the following metrics: