a48e664537
Currently, alarm notification only has the alarm_id which can be used to identify an alarm. But in some use cases, user may want to use some customized information to mark the alarm. So this patch added the alarm_name field into the notification. The name of alarm is tenant unique and can be defined by user when alarm is created. When the alarm consumer (e.g. OS::Heat::ScalingPolicy) receives an alarm, it can now identify the alarm using the customized info stored in alarm_name field. Change-Id: If9ffcca3f0de8f45483f30bc30ded91dd9d40d77 Closes-Bug: #1399067
37 lines
1.2 KiB
Python
37 lines
1.2 KiB
Python
#
|
|
# Copyright 2013 eNovance
|
|
#
|
|
# Author: Julien Danjou <julien@danjou.info>
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
"""Test alarm notifier."""
|
|
|
|
from ceilometer.alarm import notifier
|
|
|
|
|
|
class TestAlarmNotifier(notifier.AlarmNotifier):
|
|
"Test alarm notifier."""
|
|
|
|
def __init__(self):
|
|
self.notifications = []
|
|
|
|
def notify(self, action, alarm_id, alarm_name, previous, current,
|
|
reason, reason_data):
|
|
self.notifications.append((action,
|
|
alarm_id,
|
|
alarm_name,
|
|
previous,
|
|
current,
|
|
reason,
|
|
reason_data))
|