FAQ

Configure iDRAC alerts for Redfish events
13 Manage iDRAC alerts by using the Redfish Eventing feature in YX3X and later PowerEdge servers
2.3.1.6 Redfish event listener
The Redfish Event Listener is a lightweight HTTP(S) server which is used to receive the events. The
configured HTTPS endpoint must be entered in the Destination property while creating the HTTP Push Style
Subscription. See https://github.com/DMTF/Redfish-Event-Listener.
2.3.2 Redfish SSE subscription
Server Sent Events (SSE) is another method of delivering the events in Redfish Eventing. As defined by the
Web Hypertext Application Technology Working Group, SSE enables a client to start a connection with a web
service and the web service can continuously push data to the client as required.
Clients can subscribe to Redfish Alert events with subscription created over an SSE channel by performing
GET on web terminals supporting SSE Protocol.
Redfish URI for SSE Alert Event streaming
1. https://<iDRAC IP>/redfish/v1/SSE (or)
2. https://<iDRAC IP>/redfish/v1/SSE?$filter=EventFormatType eq Event
Event service on receiving a “GET” request from the client makes an entry of the SSE subscription in the
subscription collection and starts streaming the alert events generated by iDRAC. The ID field of SSE used
must be same as the unique identifier of the event and the data field of SSE contains the Event Payload.
The SSE Connection can be ended by either Client or iDRAC event service. On cases when there is no data
being sent to client for more than one hour, the connection would be ended from Event Service endpoint.
When the connection is ended, the subscription entry will be removed from the subscription collection.
SSE Client Output for Alert Events
2.3.2.1 View and delete SSE subscription
Both SSE and Push Style Subscriptions will be listed here: URI: https://<iDRAC -
IP>/redfish/v1/EventService/Subscriptions
Also see the following sections:
• Delete subscription
• View subscriptions collection