openbmc_project/Dump/Create.interface.yaml

3     interface is for user to request a particular type of dump.
6     xyz.openbmc_project.Dump.Create per dump type on
7     /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9     /xyz/openbmc_project/dump/<dump type><instance-id>.
14           Method to create a manual Dump.
19                 The additional data, if any, for initiating the dump. The key in
21                 the specific type of dump either in xyz or in a domain. The
25                 in the format 'domain.Dump.Create.CreateParameters.ParamName'.
39                 dump
43           - xyz.openbmc_project.Dump.Create.Error.Disabled
44           - xyz.openbmc_project.Dump.Create.Error.QuotaExceeded
52           Additional parameters for creating the dump.
66                 Type of the BMC dump to be collected
69                 The path to a file to create the dump, for example a systemd
70                 core-dump.
73                 Specifies the type of the error that triggered the BMC dump
76                 during the dump process.
79                 The identifier for an event that triggers the BMC dump. When a
80                 BMC dump is initiated as a response to a specific system event,
82                 with that event. By linking the dump to an event ID, the system
84                 into the dump to aid in providing a clearer context.
88           Possible types of BMC Dump.
92                 Dump triggered due to application core.
95                 Dump triggered by the user.
98                 This type of dump is triggered in response to a specific error
100                 field. If no parameters are provided, a default dump will be
104                 Dump triggered due to Ramoops type error commit.
107     - default: xyz.openbmc_project.Dump.Manager
110     - namespace: /xyz/openbmc_project/dump