/openbmc/telemetry/redfish-tests/ |
H A D | test_telemetry.py | 98 telemetry, report_definitions argument 101 for i in range(telemetry.max_reports): 103 assert telemetry.max_reports == len(report_definitions.get_collection()) 105 id + str(telemetry.max_reports), 107 interval=telemetry.min_interval, 163 def test_add_report_with_metric(redfish, telemetry, report_definitions): argument 164 if len(telemetry.metrics) <= 0: 166 metric = {"MetricId": "Id1", "MetricProperties": [telemetry.metrics[0]]} 190 def test_add_report_with_many_metrics(redfish, telemetry, report_definitions): argument 191 if len(telemetry.metrics) <= 0: [all …]
|
H A D | conftest.py | 23 def telemetry(request, redfish): function
|
/openbmc/bmcweb/redfish-core/lib/ |
H A D | metric_report.hpp | 37 namespace telemetry namespace 96 telemetry::reportInterface}; in requestRoutesMetricReportCollection() 118 const std::string reportPath = telemetry::getDbusReportPath(id); in requestRoutesMetricReport() 137 telemetry::TimestampReadings>( in requestRoutesMetricReport() 138 *crow::connections::systemBus, telemetry::service, in requestRoutesMetricReport() 139 reportPath, telemetry::reportInterface, "Readings", in requestRoutesMetricReport() 142 const telemetry::TimestampReadings& ret) { in requestRoutesMetricReport() 151 telemetry::fillReport(asyncResp->res.jsonValue, in requestRoutesMetricReport() 155 telemetry::service, reportPath, telemetry::reportInterface, in requestRoutesMetricReport()
|
H A D | metric_report_definition.hpp | 60 namespace telemetry namespace 355 telemetry::toRedfishCollectionFunction(collectionFunction); in fillReportDefinition() 484 telemetry::toDbusCollectionFunction(*collectionFunction); in getUserMetric() 810 telemetry::ReadingParameters readingParams; in performAddReport() 849 telemetry::service, "/xyz/openbmc_project/Telemetry/Reports", in performAddReport() 1222 telemetry::service, telemetry::getDbusReportPath(id), in setReportMetrics() 1223 telemetry::reportInterface, in setReportMetrics() 1353 telemetry::reportInterface}; in handleMetricReportDefinitionCollectionGet() 1445 const std::shared_ptr<telemetry::AddReport>& addReportReq, in afterRetrieveUriToDbusMap() 1468 telemetry::AddReportArgs args; in handleMetricReportDefinitionsPost() [all …]
|
H A D | trigger.hpp | 54 namespace telemetry namespace 951 telemetry::Context ctx; in handleTriggerCollectionPost() 952 if (!telemetry::parsePostTriggerParams(asyncResp->res, req, ctx)) in handleTriggerCollectionPost() 987 telemetry::triggerInterface}; in requestRoutesTriggerCollection() 998 telemetry::handleTriggerCollectionPost, std::ref(app))); in requestRoutesTriggerCollection() 1014 *crow::connections::systemBus, telemetry::service, in requestRoutesTrigger() 1015 telemetry::getDbusTriggerPath(id), in requestRoutesTrigger() 1016 telemetry::triggerInterface, in requestRoutesTrigger() 1034 if (!telemetry::fillTrigger(asyncResp->res.jsonValue, in requestRoutesTrigger() 1053 telemetry::getDbusTriggerPath(id); in requestRoutesTrigger() [all …]
|
/openbmc/bmcweb/redfish-core/include/ |
H A D | registries_selector.hpp | 47 if (telemetry::header.registryPrefix == registryName) in getRegistryHeaderAndUrlFromPrefix() 49 return HeaderAndUrl{telemetry::header, telemetry::url}; in getRegistryHeaderAndUrlFromPrefix() 77 if (telemetry::header.registryPrefix == registryName) in getRegistryFromPrefix() 79 return {telemetry::registry}; in getRegistryFromPrefix()
|
/openbmc/telemetry/ |
H A D | README.md | 19 - generic and centralized way to observe telemetry data inside system 24 There are two way to build telemetry service: 39 After successful build you should be able to run telemetry binary or start unit 43 ./tests/telemetry-ut 44 ./telemetry 58 1. [OpenBMC platform telemetry design](https://github.com/openbmc/docs/blob/master/designs/telemetr…
|
H A D | xyz.openbmc_project.Telemetry.service.in | 6 ExecStart=@bindir@/telemetry
|
/openbmc/openbmc-test-automation/redfish/telemetry_service/ |
H A D | test_telemetry_report.robot | 3 Documentation Test telemetry functionality of OpenBMC. 28 [Documentation] Verify basic telemetry report creations for different metrics. 43 [Documentation] Verify error while creating telemetry report more than max report limit. 63 [Documentation] Verify basic telemetry report creations for PCIE. 81 # telemetry definition. 89 # Find and collect actual telemetry definitions. 96 [Documentation] Find actual telemetry definitions available and store. 104 # value Equivalent regex expression of telemetry definition. 124 [Documentation] Create a basic telemetry report with single metric. 130 # metric_definition_type Name of telemetry report which needs to be created. [all …]
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-class-intel_pmt | 7 devices that expose hardware telemetry using Intel Platform 16 a PMT telemetry device that exposes hardware telemetry. Each 18 may be opened and mapped or read to access the telemetry space 19 of the device. The register layout of the telemetry space is 28 (RO) The telemetry data for this telemetry device. This file 36 (RO) The GUID for this telemetry device. The GUID identifies 45 (RO) The size of telemetry region in bytes that corresponds to 53 (RO) The offset of telemetry region in bytes that corresponds to
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/opentelemetry/ |
H A D | opentelemetry-cpp_1.17.0.bb | 2 DESCRIPTION = "An Observability framework to create and manage telemetry data \ 4 HOMEPAGE = "https://github.com/open-telemetry/opentelemetry-cpp" 11 SRC_URI = "gitsm://github.com/open-telemetry/opentelemetry-cpp.git;protocol=https;branch=main \
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/telemetry/ |
H A D | telemetry_git.bb | 3 HOMEPAGE = "https://github.com/openbmc/telemetry" 15 SRC_URI = "git://github.com/openbmc/telemetry;branch=master;protocol=https"
|
/openbmc/linux/Documentation/hwmon/ |
H A D | mp2975.rst | 28 - Supports two pages 0 and 1 for telemetry and also pages 2 and 3 for 59 - 'n' is number of telemetry pages (from 1 to 2); 82 - 'n' is number of telemetry pages (from 1 to 2); 105 - 'n' is number of telemetry pages (from 1 to 2);
|
H A D | tps53679.rst | 167 telemetry supported on TPS53676 and TPS53681 only. 185 non-phase telemetry (iout1, iout2).
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/packagegroups/ |
H A D | packagegroup-obmc-apps.bb | 30 ${PN}-telemetry \ 171 SUMMARY:${PN}-telemetry = "Telemetry solution" 172 RDEPENDS:${PN}-telemetry = " \ 173 telemetry \
|
/openbmc/openbmc/meta-phosphor/classes/ |
H A D | obmc-phosphor-image.bbclass | 29 # - obmc-telemetry - OpenBMC telemetry solution 63 FEATURE_PACKAGES_obmc-telemetry ?= "packagegroup-obmc-apps-telemetry"
|
/openbmc/bmcweb/redfish-core/src/ |
H A D | dbus_log_watcher.cpp | 139 const telemetry::TimestampReadings* readings = in getReadingsForReport() 140 std::get_if<telemetry::TimestampReadings>(&found->second); in getReadingsForReport()
|
H A D | subscription.cpp | 271 const telemetry::TimestampReadings& var) in filterAndSendReports() 288 if (!telemetry::fillReport(msg, reportId, var)) in filterAndSendReports()
|
/openbmc/telemetry/tests/ |
H A D | meson.build | 15 'telemetry-ut', 17 'telemetry-ut',
|
/openbmc/docs/designs/ |
H A D | telemetry.md | 1 # OpenBMC platform telemetry 12 The BMC on server platform gathers lots of telemetry data, which has to be 14 on telemetry over the Redfish, since it is standard API for platform 19 - OpenBMC platform telemetry shall leverage DMTF's [Redfish Telemetry Model][1] 20 for exposing platform telemetry over the network. 21 - OpenBMC platform telemetry shall leverage the [OpenBMC sensors architecture 23 - OpenBMC platform telemetry shall implement a service, called Telemetry to deal 33 Telemetry service requires telemetry sources to be implemented as D-Bus 44 - Metric Reports - contains actual metric reports containing telemetry data 49 OpenBMC telemetry architecture is shown on the diagram below. [all …]
|
/openbmc/linux/drivers/platform/chrome/wilco_ec/ |
H A D | Kconfig | 34 tristate "Enable querying telemetry data from EC" 37 If you say Y here, you get support to query EC telemetry data from
|
H A D | Makefile | 10 wilco_ec_telem-objs := telemetry.o
|
/openbmc/linux/drivers/platform/x86/intel/pmt/ |
H A D | Makefile | 10 pmt_telemetry-y := telemetry.o
|
/openbmc/bmcweb/redfish-core/include/registries/ |
H A D | telemetry_message_registry.hpp | 20 namespace redfish::registries::telemetry namespace
|
/openbmc/linux/drivers/platform/x86/intel/telemetry/ |
H A D | Kconfig | 13 telemetry for Intel SoC from Apollo Lake onwards.
|