1description: > 2 This interface contains a Create method, which can be implemented to allow 3 creation of xyz.openbmc_project.Logging.Entry objects directly over D-Bus, 4 without needing the errors defined in the *.Error/metadata.yaml files. 5 6methods: 7 - name: Create 8 description: > 9 Create a xyz.openbmc_project.Logging.Entry object. 10 parameters: 11 - name: Message 12 type: string 13 description: > 14 The Message property of the event entry. 15 - name: Severity 16 type: enum[xyz.openbmc_project.Logging.Entry.Level] 17 description: > 18 The Severity property of the event entry. 19 - name: AdditionalData 20 type: dict[string, string] 21 description: > 22 The AdditionalData property of the event entry. e.g.: 23 { 24 "key1": "value1", 25 "key2": "value2" 26 } 27 ends up in AdditionaData like: 28 ["KEY1=value1", "KEY2=value2"] 29 30 - name: CreateWithFFDCFiles 31 description: > 32 Create an xyz.openbmc_project.Logging.Entry object and pass in an 33 array of file descriptors for files that contain FFDC (first failure 34 data capture) data which may be used by event log extensions that 35 support storing it with their event logs. The other arguments are the 36 same as with Create(). The FFDC argument is ignored by the base 37 phosphor-logging event logs. 38 39 When the method call is complete the descriptors must be closed and 40 the files can be deleted if desired. 41 parameters: 42 - name: Message 43 type: string 44 description: > 45 The Message property of the event entry. 46 - name: Severity 47 type: enum[xyz.openbmc_project.Logging.Entry.Level] 48 description: > 49 The Severity property of the event entry. 50 - name: AdditionalData 51 type: dict[string, string] 52 description: > 53 The AdditionalData property of the event entry. e.g.: 54 { 55 "key1": "value1", 56 "key2": "value2" 57 } 58 ends up in AdditionaData like: 59 ["KEY1=value1", "KEY2=value2"] 60 - name: FFDC 61 type: array[struct[enum[self.FFDCFormat], byte, byte, unixfd]] 62 description: > 63 File descriptors for any files containing FFDC, along with 64 metadata about the contents: 65 66 FFDCFormat- The format type of the contained data. 67 subType - The format subtype, used for the 'Custom' type. 68 version - The version of the data format, used for the 69 'Custom' 70 type. 71 unixfd - The file descriptor to the data file. 72 73 e.g.: [ 74 {"xyz.openbmc_project.Logging.Create.FFDCFormat.JSON", 0, 0, 75 5}, 76 {"xyz.openbmc_project.Logging.Create.FFDCFormat.Custom", 1, 2, 77 6} ] 78 79enumerations: 80 - name: FFDCFormat 81 description: > 82 format types 83 values: 84 - name: JSON 85 description: > 86 Valid fully formed JSON, e.g. {"foo":"bar"} 87 - name: CBOR 88 description: > 89 Valid CBOR (Concise Binary Object Representation) 90 - name: Text 91 description: > 92 ASCII text 93 - name: Custom 94 description: > 95 Something other than the above formats 96 97service_names: 98 - default: xyz.openbmc_project.Logging 99 100paths: 101 - instance: /xyz/openbmc_project/logging 102