Package org.ovirt.engine.sdk4.services

Interface EventSubscriptionsService.AddRequest

  • All Superinterfaces:
    Request<EventSubscriptionsService.AddRequest,​EventSubscriptionsService.AddResponse>
    Enclosing interface:
    EventSubscriptionsService
    public static interface EventSubscriptionsService.AddRequest
extends Request<EventSubscriptionsService.AddRequest,​EventSubscriptionsService.AddResponse>
    Add a new event-subscription to the system. An event-subscription is always added in the context of a user. For example, to add new event-subscription for `host_high_cpu_use` for user `123`, and have the notification sent to the e-mail address: `[email protected]`, send a request like this: .... POST /ovirt-engine/api/users/123/eventsubscriptions .... With a request body like this: [source,xml] ---- host_high_cpu_use
    [email protected]
     ---- The event name will become the ID of the new event-subscription entity: GET .../api/users/123/eventsubscriptions/host_high_cpu_use Note that no user id is provided in the request body. This is because the user-id (in this case 123) is already known to the API from the context. Note also that event-subscription entity contains notification-method field, but it is not provided either in the request body. This is because currently it's always set to SMTP as SNMP notifications are still unsupported by the API layer.