Name Date Size #Lines LOC

..--

redfish-tests/H--527430

src/H--7,6846,399

subprojects/H--6649

tests/H--7,8586,552

.clang-formatH A D03-Feb-20253.7 KiB137135

.clang-tidyH A D25-Dec-2025165 117

.gitignoreH A D08-Dec-20233.5 KiB178141

LICENSEH A D27-Jan-202011.1 KiB202169

OWNERSH A D28-Nov-20251.7 KiB4944

README.mdH A D12-Jan-2026944 2818

gcovr.cfgH A D02-Aug-2024213 138

meson.buildH A D09-Jul-20253.8 KiB124112

meson.optionsH A D01-Feb-20251.4 KiB6261

xyz.openbmc_project.Telemetry.service.inH A D05-Aug-2022221 1310

README.md

1# Telemetry
2
3This component implements middleware for sensors and metrics aggregation.
4
5## Capabilities
6
7This application is implementation of Telemetry proposed in OpenBMC design docs
8`[1]`.
9
10It's responsible for:
11
12- on-demand creation of metric reports,
13  - aggregated sets of sensor values available in system `[2]`,
14- access to metric report in both pull and push model (triggers),
15- run-time monitoring of sensor`[3]` updates.
16
17## Use-cases
18
19- generic and centralized way to observe telemetry data inside system
20- back-end for Redfish TelemetryService`[4]`
21
22## References
23
241. [OpenBMC platform telemetry design](https://github.com/openbmc/docs/blob/master/designs/telemetry.md)
252. [Sensor support for OpenBMC](https://github.com/openbmc/docs/blob/master/architecture/sensor-architecture.md)
263. [dbus-sensors](https://github.com/openbmc/dbus-sensors)
274. [Redfish TelemetryService](https://redfish.dmtf.org/schemas/v1/TelemetryService.json)
28