Fix a few nits in events-listener spec
Minor edits to polish the specification. Change-Id: Iab9bfd91359586aa1b389f8bd7c45b9bc7e0cc90 Story: 2003023 Task: 23047
This commit is contained in:
parent
abb3854784
commit
551984592f
|
@ -218,7 +218,6 @@ Proposed change
|
||||||
|
|
||||||
#. Monasca Events API allows a field called 'payload' which can be in an arbitrary
|
#. Monasca Events API allows a field called 'payload' which can be in an arbitrary
|
||||||
nested JSON format.
|
nested JSON format.
|
||||||
TODO: mappings
|
|
||||||
|
|
||||||
Example Monasca Event Format:
|
Example Monasca Event Format:
|
||||||
|
|
||||||
|
@ -394,7 +393,7 @@ Alternative Solutions
|
||||||
architecture.
|
architecture.
|
||||||
* Regions may also cause separation of RabbitMQ instances that need to be monitored.
|
* Regions may also cause separation of RabbitMQ instances that need to be monitored.
|
||||||
* While it might be possible to have a service/agent in each Cell publish back to
|
* While it might be possible to have a service/agent in each Cell publish back to
|
||||||
a centralized to Kafka directly, our authentication and networking for Kafka was
|
a centralized Kafka directly, our authentication and networking for Kafka was
|
||||||
not designed to support that.
|
not designed to support that.
|
||||||
|
|
||||||
#. OpenStack Panko [5]_ is a event storage and REST API for Ceilometer and could
|
#. OpenStack Panko [5]_ is a event storage and REST API for Ceilometer and could
|
||||||
|
@ -460,6 +459,10 @@ Performance Impact
|
||||||
#. The proposed Monasca Event Listener is a new service, so performance is unknown. However, the
|
#. The proposed Monasca Event Listener is a new service, so performance is unknown. However, the
|
||||||
Monasca API has been shown to have a high performance throughput.
|
Monasca API has been shown to have a high performance throughput.
|
||||||
|
|
||||||
|
#. If any part of the Monasca notification pipeline goes down, notifications could back-up in
|
||||||
|
RabbitMQ and bring down the cluster. The risk of this could be mitigated by using a
|
||||||
|
separate RabbitMQ instance for notifications.
|
||||||
|
|
||||||
|
|
||||||
Other deployer impact
|
Other deployer impact
|
||||||
---------------------
|
---------------------
|
||||||
|
|
Loading…
Reference in New Issue