Create a resource that can receive alarms and save them as an event

Registered by Angus Salkeld

So this is a very simple resource that a user can point an alarm to inorder to record important events in their stack.

This is inspired by the AWS::SNS::Topic. We don't yet have a sns so lets at least give the use a way to store events.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Angus Salkeld
Definition:
Obsolete
Series goal:
None
Implementation:
Deferred
Milestone target:
None
Completed by
Steve Baker

Related branches

Sprints

Whiteboard

recorder:
    Type: OS::Heat::EventRecorder

  CPUAlarmHigh:
    Type: OS::Metering::Alarm
    Properties:
      counter_name: cpu_util
      statistic: avg
      period: '60'
      evaluation_periods: '1'
      threshold: '50'
      alarm_actions:
      - {"Fn::GetAtt": [WebServerScaleUpPolicy, AlarmUrl]}
        {"Fn::GetAtt": [recorder, AlarmUrl]}
      ok_actions:
      - {"Fn::GetAtt": [recorder, AlarmUrl]}
      insufficient_data_actions:
      - {"Fn::GetAtt": [recorder, AlarmUrl]}
      matching_metadata: {'metadata.user_metadata.server_group': 'WebServerGroup'}
      comparison_operator: gt

(SpamapS) I'm a bit concerned that there is no way to purge events in the API. Because of that, this seems like the wrong place to be storing something that may happen quite often. With a few big unstable stacks the events table is going to get very big, very quickly.

Gerrit topic: https://review.openstack.org/#q,topic:bp/event-recorder,n,z

Addressed by: https://review.openstack.org/40215
    Add the enabled property to the ceilometer alarm.

Addressed by: https://review.openstack.org/40216
    Add OS::Heat::EventRecorder

Addressed by: https://review.openstack.org/40328
    Stop coping UUIDStub, put it in tests.utils

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.