Nit: Aligning the content.
The index are not aligned on the following page for different tranports: http://docs.openstack.org/developer/ceilometer/architecture.html Change-Id: I8ec4539f55e88d7adfd0cb28ca8bc2341958b6d7
This commit is contained in:
parent
bd6f4cc9f2
commit
5b941f9ac7
@ -197,12 +197,14 @@ Publishing the data
|
|||||||
|
|
||||||
This figure shows how a sample can be published to multiple destinations.
|
This figure shows how a sample can be published to multiple destinations.
|
||||||
|
|
||||||
Currently, processed data can be published using 5 different transports:
|
Currently, processed data can be published using 5 different transports:
|
||||||
1. direct, which publishes samples to a configured dispatcher directly, default is database dispatcher;
|
|
||||||
2. notifier, a notification based publisher which pushes samples to a message queue
|
1. direct, which publishes samples to a configured dispatcher directly, default
|
||||||
which can be consumed by the collector or an external system;
|
is database dispatcher;
|
||||||
3. udp, which publishes samples using UDP packets;
|
2. notifier, a notification based publisher which pushes samples to a message queue
|
||||||
4. http, which targets a REST interface;
|
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
|
5. kafka, which publishes data to a Kafka message queue to be consumed by any system
|
||||||
that supports Kafka.
|
that supports Kafka.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user