SQLAlchemy storage backend.
Bases: ceilometer.alarm.storage.base.Connection
Put the data into a SQLAlchemy database.
Tables:
- meter
- meter definition
- { id: meter def id
name: meter name
type: meter type
unit: meter unit
}
- sample
- the raw incoming data
- { id: sample id
meter_id: meter id (->meter.id)
user_id: user uuid
project_id: project uuid
resource_id: resource uuid
source_id: source id
resource_metadata: metadata dictionaries
volume: sample volume
timestamp: datetime
message_signature: message signature
message_id: message uuid
}
Create an alarm.
Parameters: | alarm – The alarm to create. |
---|
Delete an alarm
Parameters: | alarm_id – ID of the alarm to delete |
---|
Yields list of AlarmChanges describing alarm history
Changes are always sorted in reverse order of occurrence, given the importance of currency.
Segregation for non-administrative users is done on the basis of the on_behalf_of parameter. This allows such users to have visibility on both the changes initiated by themselves directly (generally creation, rule changes, or deletion) and also on those changes initiated on their behalf by the alarming service (state transitions after alarm thresholds are crossed).
Parameters: |
|
---|---|
Project type: | Optional change type |
Yields a lists of alarms that match filters
Parameters: |
|
---|
Return an iterable of model.AlarmChange objects.
Yields a lists of alarms that match filter.
Record alarm change event.
Update an alarm.
Parameters: | alarm – the new Alarm to update |
---|