From c502e0b17a5628d06b4e3a46709d1443b01985e6 Mon Sep 17 00:00:00 2001 From: Doug Szumski Date: Tue, 25 Sep 2018 15:52:36 +0000 Subject: [PATCH] Add some missing parameters for Monasca Notification Partially-Implements: blueprint monasca-roles Change-Id: I21de7748156f8d3689ebfc29f2fc4dc5f7f36ddf --- ansible/roles/monasca/defaults/main.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ansible/roles/monasca/defaults/main.yml b/ansible/roles/monasca/defaults/main.yml index 7d3f013ba4..c5b2eb5e39 100644 --- a/ansible/roles/monasca/defaults/main.yml +++ b/ansible/roles/monasca/defaults/main.yml @@ -98,6 +98,13 @@ monasca_raw_logs_topic: "logs" monasca_transformed_logs_topic: "transformed-logs" monasca_events_topic: "events" monasca_alarm_state_transitions_topic: "alarm-state-transitions" +monasca_alarm_notifications_topic: "alarm-notifications" +monasca_alarm_notifications_retry_topic: "retry-notifications" +monasca_periodic_notifications_topic: "60-seconds-notifications" + +# NOTE(dszumski): Due to the way monasca-notification is currently +# implemented it is not recommended to change this period. +monasca_periodic_notifications_period: 60 # Processing pipeline threads. In a large scale deployment you will likely # want to tune these with finer precision. For example, if you have a very