pub struct LogEntry {Show 45 fields
pub odata_context: Option<Context>,
pub odata_etag: Option<Etag>,
pub odata_id: Id,
pub odata_type: Type,
pub actions: Option<Actions>,
pub additional_data_size_bytes: Option<i64>,
pub additional_data_uri: Option<String>,
pub cper: Option<CPER>,
pub cxl_entry_type: Option<CXLEntryType>,
pub created: Option<String>,
pub description: Option<Description>,
pub diagnostic_data: Option<String>,
pub diagnostic_data_type: Option<LogDiagnosticDataTypes>,
pub entry_code: Option<LogEntryCode>,
pub entry_type: LogEntryType,
pub event_group_id: Option<i64>,
pub event_id: Option<String>,
pub event_timestamp: Option<String>,
pub event_type: Option<EventType>,
pub first_overflow_timestamp: Option<String>,
pub generator_id: Option<String>,
pub id: Id,
pub last_overflow_timestamp: Option<String>,
pub links: Option<Links>,
pub message: Option<String>,
pub message_args: Option<Vec<String>>,
pub message_id: Option<String>,
pub modified: Option<String>,
pub name: Name,
pub oem_diagnostic_data_type: Option<String>,
pub oem: Option<Oem>,
pub oem_log_entry_code: Option<String>,
pub oem_record_format: Option<String>,
pub oem_sensor_type: Option<String>,
pub originator: Option<String>,
pub originator_type: Option<OriginatorTypes>,
pub overflow_error_count: Option<i64>,
pub persistency: Option<bool>,
pub resolution: Option<String>,
pub resolved: Option<bool>,
pub sensor_number: Option<i64>,
pub sensor_type: Option<SensorType>,
pub service_provider_notified: Option<bool>,
pub severity: Option<EventSeverity>,
pub specific_event_exists_in_group: Option<bool>,
}Expand description
The LogEntry schema defines the record format for a log. It is designed for Redfish event logs, OEM-specific log formats, and the IPMI System Event Log (SEL). The EntryType field indicates the type of log and the resource includes several additional properties dependent on the EntryType.
Fields§
§odata_context: Option<Context>§odata_etag: Option<Etag>§odata_id: Id§odata_type: Type§actions: Option<Actions>§additional_data_size_bytes: Option<i64>The size of the additional data for this log entry.
additional_data_uri: Option<String>The URI at which to access the additional data for this log entry, such as diagnostic data, image captures, or other files.
cper: Option<CPER>§cxl_entry_type: Option<CXLEntryType>§created: Option<String>The date and time when the log entry was created.
description: Option<Description>§diagnostic_data: Option<String>A Base64-encoded set of diagnostic data associated with this log entry.
diagnostic_data_type: Option<LogDiagnosticDataTypes>§entry_code: Option<LogEntryCode>§entry_type: LogEntryType§event_group_id: Option<i64>An identifier that correlates events with the same cause.
event_id: Option<String>The unique instance identifier for an event.
event_timestamp: Option<String>The date and time when the event occurred.
event_type: Option<EventType>§first_overflow_timestamp: Option<String>The timestamp of the first overflow captured after this log entry.
generator_id: Option<String>An identifier of the device that has generated the IPMI SEL Event Record.
id: Id§last_overflow_timestamp: Option<String>The timestamp of the last overflow captured after this log entry.
links: Option<Links>§message: Option<String>The message of the log entry. This property decodes from the entry type. If the entry type is Event, this property contains a message. If the entry type is SEL, this property contains an SEL-specific message. If the entry type is CXL, this property contains a CXL event record. Otherwise, this property contains an OEM-specific log entry. In most cases, this property contains the actual log entry.
message_args: Option<Vec<String>>The arguments for the message.
message_id: Option<String>The MessageId, event data, or OEM-specific information. This property decodes from the entry type. If the entry type is Event, this property contains a Redfish Specification-defined MessageId. If the entry type is SEL, this property contains the Event Data. Otherwise, this property contains OEM-specific information.
modified: Option<String>The date and time when the log entry was last modified.
name: Name§oem_diagnostic_data_type: Option<String>The OEM-defined type of data available in the DiagnosticData property or retrieved from the URI specified by the AdditionalDataURI property.
oem: Option<Oem>§oem_log_entry_code: Option<String>The OEM-specific entry code, if the LogEntryCode type is OEM.
oem_record_format: Option<String>The OEM-specific format of the entry. If the entry type is Oem, this property contains more information about the record format from the OEM.
oem_sensor_type: Option<String>The OEM-specific sensor type if the sensor type is OEM.
originator: Option<String>The source of the log entry.
originator_type: Option<OriginatorTypes>§overflow_error_count: Option<i64>The count of overflow errors that occurred after this log entry.
persistency: Option<bool>Indicates whether the log entry is persistent across a cold reset of the device.
resolution: Option<String>Used to provide suggestions on how to resolve the situation that caused the log entry.
resolved: Option<bool>Indicates if the cause of the log entry has been resolved or repaired.
sensor_number: Option<i64>The IPMI-defined sensor number.
sensor_type: Option<SensorType>§service_provider_notified: Option<bool>Indicates if the log entry has been sent to the service provider.
severity: Option<EventSeverity>§specific_event_exists_in_group: Option<bool>Indicates this log entry is equivalent to a more specific log entry within the same EventGroupId.