| commit | 53fb785568946ef22dd79dde100bb6d77a58f080 | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@ieisystem.com> | Tue Aug 06 13:31:55 2024 +0800 |
| committer | Adrian Ambrożewicz <adrian.ambrozewicz@linux.intel.com> | Tue Aug 20 08:20:08 2024 +0000 |
| tree | ea96936e830242ac0ea5512a98eddb0c48367447 | |
| parent | 031ebcafb7af06af9705eab1cb8f9ec9fea16969 [diff] |
Fix MD034 warnings The following warnings are generated by using markdownlint analysis: ``` redfish-tests/README.md:23:4 MD034/no-bare-urls Bare URL used [Context: "https://localhost:443"] redfish-tests/README.md:23:38 MD034/no-bare-urls Bare URL used [Context: "https://localhost:4443"] ``` Refer to markdown-lint [1] to fix MD034 [1]: https://github.com/updownpress/markdown-lint/blob/master/rules/034-no-bare-urls.md Signed-off-by: George Liu <liuxiwei@ieisystem.com> Change-Id: I90856ee4a0eb9b0079614207e0c16c679e578bf9
This component implements middleware for sensors and metrics aggregation.
This application is implementation of Telemetry proposed in OpenBMC design docs [1].
It's responsible for:
[2],[3] updates.[4]There are two way to build telemetry service:
To build it using bitbake follow the guide from OpenBMC docs[5]. To build it using meson follow the quick guide to install meson[6] and then run below commands
meson build
cd build
ninja
After successful build you should be able to run telemetry binary or start unit tests
./tests/telemetry-ut ./telemetry
In case if system is missing boost dependency, it is possible to build it locally and set BOOST_ROOT environment variable to location of built files for meson. After this change meson should be able to detect boost dependency. See [7] for more details.
More information can be found in OpenBMC docs repository [8].