Relevant data items for the error (e.g. images, internal states).

Error description. (e.g. error type & message, properties of error)

Structured data about an error that occurred within the stack, which has the purpose to be used for error resolution. This data is typically logged to the DataLogger as a payload of a LogItem, and collected by the ErrorService for processing. It contains a description, resolution instructions and relevant associated data (e.g. images, internal states etc.).

DIFFERENCE BETWEEN absl.Status / rpc.Status AND ErrorReport: - absl.Status & rpc.Status are used throughout our stack to propagate information that is useful for the respective higher level component to interpret the status, and automatically act on it. - ErrorReport: Structured data about an error event that contains a detailed context (e.g. camera images, simulation state, other internal states) which is useful to present an explanation for the error to a human and to (automatically) search for or generate resolution suggestions. The proto should contain enough data to clearly share issues with other humans and preferably enough data to replay / tune the problematic part in isolation. An ErrorReport contains the respective StatusProto (generated from absl.Status) in its description. ErrorReports should only be logged close to the root cause of the error, and at key framework locations (skill interface and executive interface).

Note that the LogItem.Metadata used in conjunction with an ErrorReport informs about timings and details about the event source (component, app name, cluster etc.). The LogItem.Context informs about how an ErrorReport is related to other ErrorReports given their context.

Instructions for resolution. Human-readable and additional structured data for recoveries which the user can select via a frontend. Instructions can reference data items from 'data'.