docs/designs/telemetry.md

46 - Metric Reports - contains actual metric reports containing telemetry data
268 metric reports. All operations on metric reports shall be done in the Telemetry
289 /xyz/openbmc_project/Telemetry/Reports
299 reports supported simultaneously.
310 periodically updated reports).
531 reports over D-Bus for the Telemetry Service. Each D-Bus sensor is mapped to
672 only. All reports was created with
674 workload. In the configuration with 50 reports and 50 sensors it is about 200
675 new readings per second, generating 200 reading reports per second. The table
683 | Idle (0 reports, 0 sensors)                   | 5188 B | 1%   | 0%     |
685 | 2 reports, 1 sensor                           | 5188 B | 1%   | 1%     |
686 | 2 reports, 2 sensors (1 sensor per report)    | 5188 B | 1%   | 1%     |
688 | 10 reports, 10 sensors (same for each report) | 5320 B | 1%   | 1-2%   |
689 | 2 reports, 20 sensors (10 per report)         | 5188 B | 1%   | 1%     |
690 | 30 reports, 30 sensors (10 per report)        | 5444 B | 1%   | 5-9%   |
691 | 50 reports, 50 sensors (10 per report)        | 5572 B | 1%   | 11-14% |
695 reading reports to obtain the desired amount of 30 or 50 reading reports.
713   which means, that Telemetry's reading reports can be directly mapped to
714   Redfish Metric Reports.
751 configuration Telemetry service provides metric reports and triggers management.
754 but in such case, collectd does not provide metric reports and triggers support
756 supported or metric reports and triggers support has to be provided by the
787 First step is for testing the Telemetry metric reports management. Test scenario
804 required set of features. The tests shall create a lot of metric reports (up to