Concept Guide

Document 365/385
"EventTypes": ["MetricReport"],
"SubscriptionType":"RedfishEvent“,
"MetricReportDefinitions":[
{
"@odata.id":
"/redfish/v1/TelemetryService/MetricReportDefinitions/<report-1>",
"@odata.id":
"/redfish/v1/TelemetryService/MetricReportDefinitions/<report-2>"
}
]
}’
View current subscription collection:
curl -s -k -u <user>:<password> -X GET https://<IDRAC-
IP>/redfish/v1/EventService/Subscriptions
-H 'Content-Type: application/json'
Delete a subscription:
curl -s -k -u <user>:<password> -X DELETE https://<IDRAC-
IP>/redfish/v1/EventService/Subscriptions/<subscrition-id>
-H 'Content-Type: application/json'
2.4.2 SSE Method
In this method Redfish client simply invokes HTTP GET on SSE URI with EventFormat type as “Metric Report”.
This establishes a connection between the client and iDRAC Telemetry Service, and all enabled reports are
streamed periodically, as configured above. This also adds an internal client subscription which gets deleted
when the connection is closed. The connection can be terminated by either the client or iDRAC Telemetry service.
If there is no telemetry data being sent to client for more than an hour, the connection gets terminated from the
service endpoint. If there is a connection issue due to a network glitch or for unknown reasons, then the last event
id is presented by the client to the service to resume streaming.
Streaming all reports:
curl -N -k - u <user>:<password> -X GET 'https://<IDRAC-
IP>/redfish/v1/SSE?$filter=EventFormatType%20eq%20MetricReport'
Streaming a single report:
curl -N -k -u <user>:<password> -X GET 'https://<IDRAC-
IP>/redfish/v1/SSE?$filter=MetricReportDefinition%20eq%20%27/redfish/v1/TelemetryService/
MetricReportDefinitions/<report>%27'