Searched full:metrics (Results 1 – 25 of 348) sorted by relevance
12345678910>>...14
| /openbmc/linux/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwell/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/haswell/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/icelake/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/skylake/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/sandybridge/ |
| D | metricgroups.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/alderlaken/ |
| D | metricgroups.json | |
| /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 …]
|
| /openbmc/linux/tools/testing/selftests/bpf/progs/ |
| D | test_cls_redirect_dynptr.c | |
| D | test_cls_redirect.c | |
| /openbmc/linux/drivers/gpu/drm/amd/pm/swsmu/smu11/ |
| D | cyan_skillfish_ppt.c | |
| /openbmc/linux/tools/perf/tests/shell/lib/ |
| D | perf_metric_validation_rules.json | |
| /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 …]
|
12345678910>>...14