Lines Matching refs:report
24 with metrics report and trigger management. This service is described later in
42 - Metric Report Definitions - defines how metric report shall be created (which
75 | | | | Metric | | Metric | |Metric report| | | | Redfish | | | |
84 | | | +--------> report <---------+ | | | | |
96 [Redfish Telemetry Model][1]. Metric report definitions uses Redfish sensors
97 URIs for metric report creation. Those sensors are also used to get URI->D-Bus
113 Telemetry service supports creating and managing metric report, which may
114 contain single or multiple metrics from sensors. This metric report is mapped to
117 The diagram below shows the flows for creation and update of metric report.
126 |Metric report definition flow| | | |
132 | | report | | | |
152 |Periodic metric report update flow| | | |
153 +----------------------------------+ +-+Metric report | |
155 | | | <-+report update | |
159 | | Send report as SSE or push-style event | | |
168 | | +-+Map report's URI <--------------------------+ |
172 | | | on report D-Bus | |PropertiesChanged | | |
174 | | +-----------------------> |to metric report timer| | |
176 | | Return metric | Return report data | |thing that triggers | | |
177 | | report in JSON <-----------------------+ |metric report update | | |
184 |On change metric report update flow| | Sensor's Properties- | |
189 | | | | |triggers report | |
194 | | Send report as SSE or push-style event | | |
203 | | +-+Map report's URI | | |
207 | | | on report D-Bus | |signal triggers the | | |
208 | | | object | |report update. It is | | |
211 | | Return metric | Return report data | |sensor triggers report| | |
212 | | report in JSON <-----------------------+ |update. | | |
219 |On demand metric report update flow| | | |
225 | | +-+Map report's URI | | |
230 | | | method for report | | |
234 | | | | |report to be updated | |
241 | | Send report as SSE or push-style event | | |
252 | | | on report D-Bus | | |
256 | | Return metric | Return report data | | |
257 | | report in JSON <-----------------------+ | |
267 service. Sending metric report as SSE or push-style events shall be done via the
268 [Redfish Event Service][6]. It is marked as optional because metric report does
271 In case of on demand metric report update, Telemetry service performs no
278 for reading report management. The second one will be used for triggers
281 **Reading report management**
283 The reading report management D-Bus object:
291 [`xyz.openbmc_project.Telemetry.ReportManager`][8] for report management. The
293 implements `AddReport` method, which is used to create a metric report. The
294 report may contain a single or multiple sensor readings. The way how the report
299 The `AddReport` method returns the path to the newly created report object. The
300 report object implements the [`xyz.openbmc_project.Object.Delete`][10] and
304 along with properties containing telemetry readings. Each report object contains
305 the timestamp of its last update. The report object contains an array of
307 this metric. Each report has also the property that stores update interval (for
356 metric report update.
365 …report which update shall be triggered when trigger condition occurs. This is optional and shall b…
416 …isting reading report. This is required when trigger's action is to update metric report. This pat…
460 report pointed by it's D-Bus path contained in trigger object properties. The
461 update shall cause the reading report's D-Bus object to emit property change
468 resources. Metric report definitions determines which metrics are to be include
469 in metric report. Metric definition is assigned to particular metric type and it
499 |Triggers | |Metric | |Metric report | |
505 | | | | | | | | report 1 | | Reads | Power |
515 | | Triggers report update | |
524 The diagram shows the relations between Redfish resources. Metric report is
568 Sample metric report definition:
600 Sample metric report:
627 Sample trigger, that will trigger metric report update:
668 statistics are shown in the table below. The reading report is mapped into
682 | 1 report, 1 sensor | 5188 B | 1% | 1% |
684 | 2 reports, 2 sensors (1 sensor per report) | 5188 B | 1% | 1% |
685 | 1 report, 10 sensors | 5188 B | 1% | 1% |
686 | 10 reports, 10 sensors (same for each report) | 5320 B | 1% | 1-2% |
687 | 2 reports, 20 sensors (10 per report) | 5188 B | 1% | 1% |
688 | 30 reports, 30 sensors (10 per report) | 5444 B | 1% | 5-9% |
689 | 50 reports, 50 sensors (10 per report) | 5572 B | 1% | 11-14% |
691 The last two configurations use 10 sensors per reading report, which gives 3 or
695 In this architecture reading report is created every time when Redfish Metric
786 shall contain creating metric report by POSTing proper metric report definition,
787 reading metric report (using GET on proper URI) and deleting the metric report.
796 scenarios with sending metric report as an event, triggering metric report
804 periodic metric report jitter, delays in event logging or sending, BMC's CPU