|
Post by ginugeorge on Dec 15, 2020 7:40:12 GMT
I am having a clarification related to an attribute "ReportActions" which is available under the MetricReportDefinitions Resource.
As per reference to the metadata file MetricReportDefinition_v1.xml, "ReportActions" attribute denotes the set of actions to perform when the metric report is generated and the allowed values are -
LogToMetricReportsCollection - When a metric report is scheduled to be generated, the service shall record the occurrence to the metric report collection found under the Telemetry Service. The Service shall update the metric report collection based on the setting of the ReportUpdates property.
RedfishEvent - When a metric report is scheduled to be generated, the service shall send an event of the MetricReport type to subscribers that the Event Subscription collection in the Event Service describes.
Now when we consider the value "LogToMetricReportsCollection" for the ReportActions attribute, there is an upper limit specified by the MaxReports attribute under the TelemetryService Resource(wrt the metadata file TelemetryService_v1.xml). Once the MetricReports Collection reaches this MaxReports limit, the service shall no longer record the report occurrence to the MetricReports collection.
Whereas, if we consider the value "RedfishEvent" for the ReportActions attribute, there is no such limit enforced and the service shall keep sending events of the MetricReport type to active subscribers.
Should this be the expected behaviour ?
or
Once the MetricReports Collection reaches this MaxReports limit, the service should neither record the occurrence to the MetricReports collection nor send any events of the MetricReport type ?
Please suggest your inputs.
|
|
|
Post by jautor on Dec 16, 2020 4:52:30 GMT
Now when we consider the value "LogToMetricReportsCollection" for the ReportActions attribute, there is an upper limit specified by the MaxReports attribute under the TelemetryService Resource(wrt the metadata file TelemetryService_v1.xml). Once the MetricReports Collection reaches this MaxReports limit, the service shall no longer record the report occurrence to the MetricReports collection. Whereas, if we consider the value "RedfishEvent" for the ReportActions attribute, there is no such limit enforced and the service shall keep sending events of the MetricReport type to active subscribers. Should this be the expected behaviour ?
Yes, that is the expected behavior. Because a Redfish Service is expected to be implemented on devices with limited memory, the "MaxReports" property allows the service to indicate that limited memory may be available for storage of metric reports. (Note that a service implementation with ample local storage could set this number to an arbitrary large number, like 10000) In addition, a "new" metric report may replace an older one if the "max" has been reached, so this can still result in new data being stored. But since generating a Redfish Event doesn't consume local storage resources (on the service end), there is no reason to limit the number of events that can be produced. Jeff
|
|