| /openbmc/openbmc-test-automation/lib/ |
| H A D | esel_utils.robot | 53 # "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
55 # "@odata.type": "#LogEntry.v1_4_0.LogEntry",
|
| H A D | logging_utils.robot | 259 # "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
261 # "@odata.type": "#LogEntry.v1_4_0.LogEntry",
350 # [@odata.type]: #LogEntry.v1_8_0.LogEntry
|
| /openbmc/docs/designs/ |
| H A D | redfish-postcodes.md | 17 The standard Redfish LogService and LogEntry schemas will be used to expose BIOS
45 [LogEntry](https://redfish.dmtf.org/schemas/LogEntry_v1.xml) schema.
56 "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
58 "@odata.type": "#LogEntry.v1_4_0.LogEntry",
192 rather than using the LogEntry schema. Use of OEM extensions to Redfish are
|
| H A D | event-logging.md | 22 ### Redfish LogEntry and Message Registry
24 In Redfish, the [`LogEntry` schema][LogEntry] is used for a range of items that
67 device and system. When this event occurs, there might be a `LogEntry` recorded
81 `MessageId` field in the `LogEntry`) and `MessageArgs` to avoid needing to
93 [LogEntry]:
94 …de0c960c4262169ea92a4b852dd5ebbe3810bf00/redfish-core/schema/dmtf/json-schema/LogEntry.v1_16_0.json
171 `Message` field of the `LogEntry`. Furthermore, these regular-expressions are
200 - Similar applications can result in different Redfish `LogEntry` for the same
281 Leverage the Redfish `LogEntry.DiagnosticData` field to provide a
319 Message Registry, and translate from `phosphor-logging` to Redfish `LogEntry`
|
| H A D | guard-on-bmc.md | 190 "@odata.type": "#LogEntry.v1_7_0.LogEntry",
|
| H A D | cper-records.md | 22 into the [LogEntry resource][logentry]. These expose a section by section
|
| H A D | hw-fault-monitor.md | 137 original fault event information. The EventGroupID in a Redfish LogEntry could
|
| /openbmc/openbmc-test-automation/redfish/systems/eventlog/ |
| H A D | test_event_logging.robot | 102 # "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
104 # "@odata.type": "#LogEntry.v1_4_0.LogEntry",
163 # "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
165 # "@odata.type": "#LogEntry.v1_4_0.LogEntry",
213 # "@odata.type": "#LogEntry.v1_8_0.LogEntry",
434 # "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
436 # "@odata.type": "#LogEntry.v1_4_0.LogEntry",
|
| /openbmc/phosphor-fan-presence/ |
| H A D | logger.hpp | 41 using LogEntry = std::tuple<std::string, std::string>; typedef in phosphor::fan::Logger
170 std::vector<LogEntry> _entries;
|
| /openbmc/openbmc-test-automation/openpower/mpipl/ |
| H A D | test_mpipl_basic.robot | 120 # "@odata.type": "#LogEntry.v1_8_0.LogEntry",
136 # "@odata.type": "#LogEntry.v1_8_0.LogEntry",
|
| /openbmc/bios-bmc-smm-error-logger/test/ |
| H A D | external_storer_file_test.cpp | 241 "@odata.type": "#LogEntry.v1_13_0.LogEntry" in TEST_F()
273 "@odata.type": "#LogEntry.v1_13_0.LogEntry" in TEST_F()
|
| /openbmc/openbmc-test-automation/redfish/systems/LogServices/ |
| H A D | test_post_codes.robot | 172 # "@odata.type": "#LogEntry.v1_8_0.LogEntry",
|
| /openbmc/bmcweb/docs/ |
| H A D | Redfish.md | 686 #### LogEntry subsubsection
930 #### LogEntry subsubsection
951 #### LogEntry subsubsection
|
| /openbmc/intel-ipmi-oem/docs/ |
| H A D | Intel_IPMI_Platform_Events.md | 338 "@odata.type": "#LogEntry.v1_4_0.LogEntry",
|
| /openbmc/openbmc-test-automation/openpower/pel/ |
| H A D | test_bmc_pel.robot | 284 # [@odata.type]: #LogEntry.v1_5_1.LogEntry
390 # [@odata.type]: #LogEntry.v1_4_0.LogEntry
|
| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_bmc_dumps.robot | 60 # "@odata.type": "#LogEntry.v1_7_0.LogEntry",
|
| /openbmc/openbmc-tools/rootfs_size/ |
| H A D | results.txt | 455 4096: /usr/share/www/redfish/v1/JsonSchemas/LogEntry
474 4096: /usr/share/www/redfish/v1/JsonSchemas/LogEntry/LogEntry.json
1783 0: /usr/share/www/redfish/v1/JsonSchemas/LogEntry/index.json
|
| /openbmc/ |
| D | opengrok1.0.log | [all...] |
| D | opengrok2.0.log | [all...] |