summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMatt Spinler <spinler@us.ibm.com>2018-02-19 15:23:32 -0600
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2018-02-27 13:53:48 +0000
commit72ceb5da488af4316aa3940e04573a650c74b480 (patch)
tree88e059afb407df4f454c86aa19f96a1daa049cec
parent85bb6f3b78701261470eb589a06f09784aa67612 (diff)
downloadphosphor-dbus-interfaces-72ceb5da488af4316aa3940e04573a650c74b480.zip
phosphor-dbus-interfaces-72ceb5da488af4316aa3940e04573a650c74b480.tar.gz
Change metadata on Critical high/low sensor errors
Feedback from the field shows it would be useful to have information about the sensors that are too high or low in the metadata rather than the type. This is a free format metadata string field so that the code that creates this error can put in whatever metadata it thinks is necessary, ideally including information about the sensor(s) in question. Tested: Built repository Change-Id: I6f790a314d132bfbdc45c90a13f9c3831163c2f1 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
-rw-r--r--xyz/openbmc_project/Sensor/Threshold.metadata.yaml4
1 files changed, 2 insertions, 2 deletions
diff --git a/xyz/openbmc_project/Sensor/Threshold.metadata.yaml b/xyz/openbmc_project/Sensor/Threshold.metadata.yaml
index fa5ff1e..1ebaf51 100644
--- a/xyz/openbmc_project/Sensor/Threshold.metadata.yaml
+++ b/xyz/openbmc_project/Sensor/Threshold.metadata.yaml
@@ -1,10 +1,10 @@
- name: CriticalHigh
level: ERR
meta:
- - str: "SENSOR_TYPE=%s"
+ - str: "SENSOR_DATA=%s"
type: string
- name: CriticalLow
level: ERR
meta:
- - str: "SENSOR_TYPE=%s"
+ - str: "SENSOR_DATA=%s"
type: string
OpenPOWER on IntegriCloud