From 9260bc2cb15a4659ce3050208b8506dc5faa8e7e Mon Sep 17 00:00:00 2001 From: gordon chung Date: Wed, 23 Sep 2015 13:50:52 -0400 Subject: [PATCH] [ceilometer] add ability to publish to multiple topics add documentation on how to use topic option. Change-Id: I7dec6849feef5d8f31ef1fe16cc7437e0b1b2e60 Closes-Bug: #1433791 --- .../source/telemetry-data-retrieval.rst | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/admin-guide-cloud/source/telemetry-data-retrieval.rst b/doc/admin-guide-cloud/source/telemetry-data-retrieval.rst index 784931996a..23a5c759dc 100644 --- a/doc/admin-guide-cloud/source/telemetry-data-retrieval.rst +++ b/doc/admin-guide-cloud/source/telemetry-data-retrieval.rst @@ -473,6 +473,14 @@ policy option can be used by ``kafka`` publisher: queue length can be configured with ``max_queue_length``, where 1024 is the default value). +The following option is additionally available for the ``notifier`` publisher: + +``topic`` + The topic name of queue to publish to. Setting this will override the + default topic defined by ``metering_topic`` and ``event_topic`` options. + This option can be used to support multiple consumers. Support for this + feature was added in Kilo. + The following options are available for the ``file`` publisher: ``max_bytes`` @@ -495,4 +503,4 @@ specified. A sample ``publishers`` section in the publishers: - udp://10.0.0.2:1234 - rpc://?per_meter_topic=1 (deprecated in Liberty) - - notifier://?policy=drop&max_queue_length=512 + - notifier://?policy=drop&max_queue_length=512&topic=custom_target