From 7b94277d8c0916044e270d0f31d41c465ec1b263 Mon Sep 17 00:00:00 2001 From: Hanxi Liu Date: Thu, 4 Aug 2016 20:33:09 +0800 Subject: [PATCH] Add a publish transport in Ceilometer architecture document Add the direct transport of publishing data in Ceilometer document, namely architecture.rst. Change-Id: I156068f61001e4e6159bcc4d85f3594d4be97e13 Closes-Bug: #1612648 --- doc/source/architecture.rst | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/doc/source/architecture.rst b/doc/source/architecture.rst index 5f89f0d559..74762f1259 100644 --- a/doc/source/architecture.rst +++ b/doc/source/architecture.rst @@ -197,12 +197,14 @@ Publishing the data This figure shows how a sample can be published to multiple destinations. -Currently, processed data can be published using 5 different transports: -notifier, a notification based publisher which pushes samples to a message -queue which can be consumed by the collector or an external system; udp, which -publishes samples using UDP packets; http, which targets a REST interface; -and kafka, which publishes data to a Kafka message queue to be consumed by any -system that supports Kafka. +Currently, processed data can be published using 5 different transports: +1. direct, which publishes samples to a configured database dispatcher directly; +2. notifier, a notification based publisher which pushes samples to a message queue + which can be consumed by the collector or an external system; +3. udp, which publishes samples using UDP packets; +4. http, which targets a REST interface; +5. kafka, which publishes data to a Kafka message queue to be consumed by any system + that supports Kafka. Storing the data