| /openbmc/telemetry/redfish-tests/ |
| H A D | test_telemetry.py | 27 assert "MetricProperties" in metricDefinition, "Missing metrics"
28 assert len(metricDefinition["MetricProperties"]) > 0, "Missing metrics"
106 metrics=[],
164 if len(telemetry.metrics) <= 0:
166 metric = {"MetricId": "Id1", "MetricProperties": [telemetry.metrics[0]]}
167 report_definitions.add_report("Test", metrics=[metric])
169 assert len(r["Metrics"]) == 1, "Invalid Metrics, different then requested"
171 r["Metrics"][0]["MetricId"] == metric["MetricId"]
174 r["Metrics"][0]["MetricProperties"] == metric["MetricProperties"]
186 "Test", metrics=[metric], code=RedfishHttpStatus.bad_request
[all …]
|
| H A D | redfish_requests.py | 65 self.metrics = []
70 self.metrics += [x for x in metricDef["MetricProperties"]]
71 self.metrics = self.metrics[:metric_limit]
85 metrics=None, argument
93 "Metrics": [],
97 if metrics is not None:
98 body["Metrics"] = metrics
|
| /openbmc/docs/designs/ |
| H A D | bmc-health-monitor.md | 11 means to make sure the BMC is working correctly. User can get required metrics
12 data as per configurations instantly. Set of monitored metrics may include CPU
25 3. Metric staging. When metrics are collected, they will be ready to be read
29 4. Data transfer, where the consumer program obtains the metrics from the BMC by
31 5. The consumer program may take certain actions based on the metrics collected.
38 differences between sensors and metrics:
40 1. Sensor data originate from hardware, while most metrics may be obtained
42 metrics on all kinds of BMCs than sensors on BMCs, and we might not need the
44 most health metrics.
45 2. Most sensors are instantaneous readings, while metrics might accumulate over
[all …]
|
| /openbmc/openbmc/meta-quanta/meta-s6q/recipes-phosphor/configuration/s6q-yaml-config/ |
| H A D | ipmi-sensors.yaml | 527 path: /xyz/openbmc_project/metrics/memory/Memory Error
551 path: /xyz/openbmc_project/metrics/memory/Other IIO Error
575 path: /xyz/openbmc_project/metrics/memory/MCERR
599 path: /xyz/openbmc_project/metrics/memory/Memory Error Dis
623 path: /xyz/openbmc_project/metrics/memory/Memory PPR
647 path: /xyz/openbmc_project/metrics/memory/Processor Misc
671 path: /xyz/openbmc_project/metrics/memory/XGMI Error
695 path: /xyz/openbmc_project/metrics/memory/POST Error
719 path: /xyz/openbmc_project/metrics/memory/PCI Error
743 path: /xyz/openbmc_project/metrics/memory/PCIe Error
[all …]
|
| /openbmc/google-misc/subprojects/metrics-ipmi-blobs/ |
| H A D | README.md | 1 # metrics-ipmi-blobs
3 IPMI BLOBs handler to export BMC metrics snapshot
8 snapshot of the BMC's health metrics, which includes the following categories:
16 The size of the metrics are usually around 1KB to 1.5KB.
|
| /openbmc/openpower-host-ipmi-oem/org/open_power/OCC/Metrics/ |
| H A D | meson.build | 3 domain = 'org.open_power.OCC.Metrics'
4 md_yaml_file = files('../Metrics.metadata.yaml')
13 install_dir: get_option('includedir') / 'org/open_power/OCC/Metrics',
23 install_dir: get_option('includedir') / 'org/open_power/OCC/Metrics',
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | PortMetrics_v1.xml | 42 …m="OData.LongDescription" String="This resource shall represent the port metrics for a switch devi…
61 … <String>/redfish/v1/Fabrics/{FabricId}/Switches/{SwitchId}/Ports/{PortId}/Metrics</String>
62 …temId}/Storage/{StorageId}/StorageControllers/{StorageControllerId}/Ports/{PortId}/Metrics</String>
63 …uterSystemId}/Storage/{StorageId}/Controllers/{StorageControllerId}/Ports/{PortId}/Metrics</String>
64 …fish/v1/Systems/{ComputerSystemId}/FabricAdapters/{FabricAdapterId}/Ports/{PortId}/Metrics</String>
65 …stems/{ComputerSystemId}/GraphicsControllers/{GraphicsControllerId}/Ports/{PortId}/Metrics</String>
66 …fish/v1/Systems/{ComputerSystemId}/USBControllers/{USBControllerId}/Ports/{PortId}/Metrics</String>
67 …ing>/redfish/v1/Systems/{ComputerSystemId}/Processors/{ProcessorId}/Ports/{PortId}/Metrics</String>
68 …redfish/v1/Chassis/{ChassisId}/MediaControllers/{MediaControllerId}/Ports/{PortId}/Metrics</String>
69 …ng>/redfish/v1/Chassis/{ChassisId}/FabricAdapters/{FabricAdapterId}/Ports/{PortId}/Metrics</String>
[all …]
|
| H A D | SwitchMetrics_v1.xml | 43 …<Annotation Term="OData.LongDescription" String="This resource shall represent the metrics for a s…
84 <Annotation Term="OData.Description" String="The memory metrics for a switch."/>
85 …n" String="This property shall contain properties that describe the memory metrics for a switch."/>
95 <Annotation Term="OData.Description" String="The memory metrics for a switch."/>
96 …n" String="This property shall contain properties that describe the memory metrics for a switch."/>
98 …<Annotation Term="OData.Description" String="The memory metrics since the last reset for this swit…
99 …iption" String="This property shall contain properties that describe the metrics for the current p…
102 …<Annotation Term="OData.Description" String="The memory metrics for the lifetime of this switch."/>
103 …iption" String="This property shall contain properties that describe the metrics for the lifetime …
125 …<Annotation Term="OData.Description" String="The memory metrics since the last switch reset or `Cl…
[all …]
|
| H A D | DriveMetrics_v1.xml | 59 …String>/redfish/v1/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</String>
60 <String>/redfish/v1/Chassis/{ChassisId}/Drives/{DriveId}/Metrics</String>
61 …itionService/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</String>
62 …g>/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Metrics</String>
63 …/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</String>
64 …>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</String>
65 <String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Metrics</String>
66 …/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</String>
71 …String>/redfish/v1/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</String>
72 …itionService/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</String>
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | SwitchMetrics.v1_1_0.json | 71 …"description": "The memory metrics since the last switch reset or `ClearCurrentPeriod` action for …
72 …"longDescription": "This type shall describe the memory metrics since the last reset or `ClearCurr…
111 "description": "The memory metrics for a switch.",
112 …cription": "This property shall contain properties that describe the memory metrics for a switch.",
130 "description": "The memory metrics since the last reset for this switch.",
131 …gDescription": "This property shall contain properties that describe the metrics for the current p…
135 "description": "The memory metrics for the lifetime of this switch.",
136 …gDescription": "This property shall contain properties that describe the metrics for the lifetime …
143 "description": "The memory metrics for the lifetime for a switch.",
144 …"longDescription": "This type shall describe the memory metrics since manufacturing for a switch.",
[all …]
|
| H A D | PortMetrics.v1_8_0.json | 39 "description": "The port metrics specific to CXL ports.",
40 "longDescription": "This type shall contain the port metrics specific to CXL ports.",
69 "description": "The Fibre Channel-specific port metrics for network ports.",
70 … "longDescription": "This type shall describe Fibre Channel-specific metrics for network ports.",
242 "description": "The port metrics for a Gen-Z interface.",
243 "longDescription": "This type shall describe the Gen-Z related port metrics.",
363 …"description": "The port metrics for network ports, including Ethernet, Fibre Channel, and InfiniB…
364 …"longDescription": "This type shall describe the metrics for network ports, including Ethernet, Fi…
747 …"longDescription": "This resource shall represent the port metrics for a switch device or componen…
782 "description": "The port metrics specific to CXL ports.",
[all …]
|
| H A D | MetricReportDefinition.v1_4_7.json | 119 …n": "Specifies a set of metrics to include in the metric report. Calculation parameters, if prese…
120 …"longDescription": "The properties shall specify a set of metrics to include in the metric report.…
205 …"description": "The `MetricReportDefinition` schema describes set of metrics that are collected in…
206 …"longDescription": "This resource shall specify a set of metrics that shall be collected into a me…
320 "Metrics": { object
321 …"description": "The list of metrics to include in the metric report. The metrics might include ca…
325 …scription": "The property shall contain a list of metrics to include in the metric report. The me…
374 …metrics are suppressed from the generated metric report. If `true`, any metric that equals the sa…
375 …metrics are suppressed from the generated metric report. If `true`, any metric that equals the sa…
|
| H A D | ProcessorMetrics.v1_7_0.json | 81 "description": "The processor core metrics.",
82 …"longDescription": "This type shall contain properties that describe cache metrics of a processor …
160 "description": "The total cache metrics for a processor.",
161 …"longDescription": "This property shall contain properties that describe the metrics for all of th…
179 …"description": "The cache metrics since the last reset or `ClearCurrentPeriod` action for this pro…
180 …gDescription": "This property shall contain properties that describe the metrics for the current p…
185 "description": "The cache metrics for the lifetime of this processor.",
186 …gDescription": "This property shall contain properties that describe the metrics for the lifetime …
227 "description": "The processor core metrics.",
253 "description": "The cache metrics of this core in the processor.",
[all …]
|
| /openbmc/openbmc/meta-google/recipes-google/ipmi/ |
| H A D | metrics-ipmi-blobs_git.bb | 1 SUMMARY = "gBMC Health Metrics Blob"
2 DESCRIPTION = "BMC health metrics IPMI blob handler."
3 GOOGLE_MISC_PROJ = "metrics-ipmi-blobs"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-gnome/gtk+/gtk+/ |
| H A D | toggle-font.diff | 62 + PangoFontMetrics *metrics;
66 + metrics = pango_context_get_metrics (context,
70 + height = pango_font_metrics_get_ascent (metrics) +
71 + pango_font_metrics_get_descent (metrics);
73 + pango_font_metrics_unref (metrics);
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | MetricReportDefinition.v1_4_7.json | 119 …n": "Specifies a set of metrics to include in the metric report. Calculation parameters, if prese…
120 …"longDescription": "The properties shall specify a set of metrics to include in the metric report.…
205 …"description": "The `MetricReportDefinition` schema describes set of metrics that are collected in…
206 …"longDescription": "This resource shall specify a set of metrics that shall be collected into a me…
320 "Metrics": { object
321 …"description": "The list of metrics to include in the metric report. The metrics might include ca…
325 …scription": "The property shall contain a list of metrics to include in the metric report. The me…
374 …metrics are suppressed from the generated metric report. If `true`, any metric that equals the sa…
375 …metrics are suppressed from the generated metric report. If `true`, any metric that equals the sa…
|
| /openbmc/telemetry/src/ |
| H A D | metric.hpp | 8 #include "metrics/collection_data.hpp"
33 metrics::CollectionData& findAssociatedData(
41 std::vector<std::unique_ptr<metrics::CollectionData>> collectionAlgorithms;
|
| H A D | report.cpp | 40 objServer(objServer), metrics(std::move(metricsIn)), timer(ioc), in Report()
45 toReadingParameters(utils::transform(metrics, [](const auto& metric) { in Report()
126 for (auto& metric : metrics) in activate()
136 for (auto& metric : metrics) in deactivate()
146 const std::vector<std::shared_ptr<interfaces::Metric>>& metrics) in getMetricCount() argument
149 for (auto& metric : metrics) in getMetricCount()
293 reportFactory.updateMetrics(metrics, in makeReportInterface()
297 utils::transform(metrics, [](const auto& metric) { in makeReportInterface()
300 metricCount = getMetricCount(metrics); in makeReportInterface()
403 for (auto& metric : self.metrics) in timerProcForOnChangeReport()
[all …]
|
| H A D | report_factory.cpp | 28 auto metrics = utils::transform( in make() local
45 reportStorage, std::move(metrics), *this, enabled, in make()
50 std::vector<std::shared_ptr<interfaces::Metric>>& metrics, bool enabled, in updateMetrics() argument
53 std::vector<std::shared_ptr<interfaces::Metric>> oldMetrics = metrics; in updateMetrics()
93 metrics = std::move(newMetrics); in updateMetrics()
|
| /openbmc/openbmc/poky/meta/recipes-core/meta/ |
| H A D | cve-update-nvd2-native.bb | 356 accessVector = elt['cve']['metrics']['cvssMetricV2'][0]['cvssData']['accessVector']
357 vectorString = elt['cve']['metrics']['cvssMetricV2'][0]['cvssData']['vectorString']
358 cvssv2 = elt['cve']['metrics']['cvssMetricV2'][0]['cvssData']['baseScore']
363 …accessVector = accessVector or elt['cve']['metrics']['cvssMetricV30'][0]['cvssData']['attackVector…
364 …vectorString = vectorString or elt['cve']['metrics']['cvssMetricV30'][0]['cvssData']['vectorString…
365 cvssv3 = elt['cve']['metrics']['cvssMetricV30'][0]['cvssData']['baseScore']
369 …accessVector = accessVector or elt['cve']['metrics']['cvssMetricV31'][0]['cvssData']['attackVector…
370 …vectorString = vectorString or elt['cve']['metrics']['cvssMetricV31'][0]['cvssData']['vectorString…
371 cvssv3 = cvssv3 or elt['cve']['metrics']['cvssMetricV31'][0]['cvssData']['baseScore']
376 …accessVector = accessVector or elt['cve']['metrics']['cvssMetricV40'][0]['cvssData']['attackVector…
[all …]
|
| /openbmc/docs/tof/ |
| H A D | membership-and-voting.md | 42 … contributions close for OpenBMC Development Community membership eligibility (See “Metrics”). |
80 highly-productive. It is the responsibility of the TOF to set metrics for
86 determining metrics for the next election / membership cycle.) In any election
91 by the existing metrics may petition the TOF for inclusion in either tier and
95 significant support activities in areas not covered by existing metrics such as
108 ### Metrics subsection
|
| /openbmc/telemetry/src/metrics/ |
| H A D | collection_data.cpp | 1 #include "metrics/collection_data.hpp"
3 #include "metrics/collection_function.hpp"
5 namespace metrics namespace
159 } // namespace metrics
|
| H A D | collection_function.hpp | 11 namespace metrics namespace
29 } // namespace metrics
|
| H A D | collection_data.hpp | 12 namespace metrics namespace
31 } // namespace metrics
|
| /openbmc/openbmc/meta-openpower/recipes-phosphor/ipmi/ |
| H A D | openpower-ipmi-oem-error-native_git.bb | 17 install ${SRC}/Metrics.errors.yaml ${DEST}
18 install ${SRC}/Metrics.metadata.yaml ${DEST}
|