30c9334306
Takes a yaml-based config file (see etc/oslo/routing_notifier.yaml.sample) via routing_notifier_config option. Events may be routed by priority or event_type. Implements: blueprint configurable-notification Change-Id: I437dfac348f387044e6da3d6a0bbb208323c1741
30 lines
738 B
Plaintext
30 lines
738 B
Plaintext
# Setting a priority AND an event means both have to be satisfied.
|
|
#
|
|
# However, defining different sets for the same driver allows you
|
|
# to do OR operations.
|
|
#
|
|
# See how this logic is modeled below:
|
|
#
|
|
# if (priority in info, warn or error) or
|
|
# (event == compute.scheduler.run_instance)
|
|
# send to messaging driver ...
|
|
#
|
|
# if priority == 'poll' and
|
|
# event == 'bandwidth.*'
|
|
# send to poll driver
|
|
|
|
group_1:
|
|
messaging:
|
|
accepted_priorities: ['info', 'warn', 'error']
|
|
|
|
poll:
|
|
accepted_priorities: ['poll']
|
|
accepted_events: ['bandwidth.*']
|
|
|
|
log:
|
|
accepted_events: ['compute.instance.exists']
|
|
|
|
group_2:
|
|
messaging:⋅
|
|
accepted_events: ['compute.scheduler.run_instance.*']
|