openstack/vitrage
Code Issues Proposed changes

use 'alarm_name' not 'alarm_type' in properties of raise_alarm

Browse Source 
action in the example template

Change-Id: I42531db016c4a47f372122bfb4d7c4a127def974
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
This commit is contained in:
dongwenjuan 2016-05-30 16:49:40 +08:00
parent 5360c43132
commit 95c4156f79
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/vitrage-template-format.rst
View File

@ -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