glance/doc/source/notifications.rst
Johannes Erdfelt 091aae8a6d Add notifications for uploads, updates and deletes
Change-Id: I372f77fe2d1a575f2108c9b8d1f69301c0d5eb5e
2011-08-15 19:58:57 +00:00

1.8 KiB

Notifications

Notifications can be generated for each upload, update or delete image event. These can be used for auditing, troubleshooting, etc.

Strategies

  • logging

    This strategy uses the standard Python logging infrastructure with the notifications ending up in file specificed by the log_file configuration directive.

  • rabbit

    This strategy sends notifications to a rabbitmq queue. This can then be processed by other services or applications.

  • noop

    This strategy produces no notifications. It is the default strategy.

Content

Every message contains a handful of attributes.

  • message_id

    UUID identifying the message.

  • publisher_id

    The hostname of the glance instance that generated the message.

  • event_type

    Event that generated the message.

  • priority

    One of WARN, INFO or ERROR.

  • timestamp

    UTC timestamp of when event was generated.

  • payload

    Data specific to the event type.

Payload

WARN and ERROR events contain a text message in the payload.

  • image.upload

    For INFO events, it is the image metadata.

  • image.update

    For INFO events, it is the image metadata.

  • image.delete

    For INFO events, it is the image id.