From abacf402a837d3649e70a93cc92d2eef9b22c58b Mon Sep 17 00:00:00 2001 From: WenyanZhang Date: Fri, 26 Aug 2016 11:05:30 +0800 Subject: [PATCH] correct the meaning of direct publish transport Now the direct publish transport is not only for database dispatcher, but also could been setted to all methods in dispatcher. The source code change is Change-Id: I9dc48f25ba6d846ee75785ee529798af5085a53a. This commit is to modify the relevnet document. Change-Id: I2dd4cab34d0b84e3eedff95134321ae0388affa2 Closes-Bug: #1617126 --- doc/source/architecture.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/architecture.rst b/doc/source/architecture.rst index 74762f1259..09a6290931 100644 --- a/doc/source/architecture.rst +++ b/doc/source/architecture.rst @@ -198,7 +198,7 @@ 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: -1. direct, which publishes samples to a configured database dispatcher directly; +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 which can be consumed by the collector or an external system; 3. udp, which publishes samples using UDP packets;