From 95c4156f79da4062159ff732c9c16db8a65b2cbc Mon Sep 17 00:00:00 2001 From: dongwenjuan Date: Mon, 30 May 2016 16:49:40 +0800 Subject: [PATCH] use 'alarm_name' not 'alarm_type' in properties of raise_alarm action in the example template Change-Id: I42531db016c4a47f372122bfb4d7c4a127def974 Signed-off-by: dongwenjuan --- doc/source/vitrage-template-format.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/vitrage-template-format.rst b/doc/source/vitrage-template-format.rst index 863a58578..e6a7269fd 100644 --- a/doc/source/vitrage-template-format.rst +++ b/doc/source/vitrage-template-format.rst @@ -127,7 +127,7 @@ The following template demonstrates - action: action_type: raise_alarm properties: - alarm_type: instance_mem_performance_problem + alarm_name: instance_mem_performance_problem severity: warning action_target: target: instance # entity template_id @@ -209,7 +209,7 @@ case-insensitive. - action: action_type: raise_alarm properties: - alarm_type: host_in_error_state + alarm_name: host_in_error_state severity: critical action_target: target: host_in_error @@ -274,7 +274,7 @@ an alarm on the hosting zone or an alarm on the hosting host. - action: action_type : raise_alarm properties: - alarm_type: instance_connectivity_problem + alarm_name: instance_connectivity_problem severity: critical action_target: target: instance