Skip to main content

GET – Log Entry Instance

Request​

Chassis

GET https://{{ip}}/redfish/v1/Chassis/{{chassis_instance}}/LogServices/{{chassis_log_instance}}/
Entries/{{chassis_logentry_instance}}
Content-Type: application/json

Manager

GET https://{{ip}}/redfish/v1/Managers/{{manager_instance}}/LogServices/{{manager_log_instance}}/
Entries/{{manager_logentry_instance}}
Content-Type: application/json

System

GET https://{{ip}}/redfish/v1/Systems/{{system_instance}}/LogServices/{{system_log_instance}}/Entries/
{{system_logentry_instance}}
Content-Type: application/json

Telemetry

GET https://{{ip}}/redfish/v1/TelemetryService/LogService/Entries/{{logentry_instance}}
Content-Type: application/json

Response​

The response of the request will be in JSON format. The properties are mentioned in the following table.

Table 1. Log Entry Property

Name

Type

Read only

Description

(OData Attributes)  

Refer to OData Support

OemObject 

OEM Extension (Optional), Refer to Resource Complex Types

Id(M)StringTrue

Refer to Resource Type Definitions

Name(M)StringTrue
DescriptionStringTrue

Severity

String

True

  1. This is the severity of the log entry.

  2. It can take any one of the Enum values: OK, Warning or Critical.

Created

String

True

The time the log entry was created.

EventId

String

True

  1. If present, this LogEntry records an Event and the value shall indicate a unique identifier for the event, the format of which is implementation dependent.

  2. This property will be populated only for EventLogs.

  3. EventId format is implementation dependent, and value will be string of a positive integer.

EventTimestamp

String

True

If present, this LogEntry records an Event and the value shall be the time the event occurred.

EntryType(M)

String

True

  1. This property shall represent the type of LogEntry.

  2. If the resource represents an IPMI SEL log entry, the value shall be SEL.

  3. If the resource represents an Event log, the value shall be Event.

  4. If the resource represents an OEM log format, the value shall be Oem. Enum can be Event,SELor Oem.

EntryCode

String

True

  1. This property shall be present if the EntryType value is SEL.

  2. Refer to EntryCode Strings

SensorType

String

True

  1. This property shall be present if the EntryType value is SEL.

  2. Refer to SensorType Strings

SensorNumber

Number

True

This property decodes from EntryType: If it is SEL, it is the sensor number, if Event it is not applicable. Otherwise, it is Oem specific

Message

String

True

  1. This property shall be the Message property of the event and decodes from EntryType.

  2. If EntryType is "Event"then it is a message description.

  3. If EntryType is "SEL"then it contain SEL Specific message otherwise "Oem"specific Log entry.

  4. In most cases, this property contains actual Log Entry.

  5. EntryType is "SEL"then Message contain SEL message format specified in Table 41-1 SEL Event Recorts in IPMI Specification v2.0 revision 1.1

MessageId

String

True

  1. This property shall the MessageId property of the event and decodes from EntryType.

  2. If EntryType is "Event"then it is a Redfish Specification-defined MessageId.

  3. If EntryType is "SEL"then it contain Event Data otherwise "Oem"specific information.

Populated for all logs.

  1. EntryType is "Event" then MessageId format will be RegistryName.MajorVersion.MinorVersion.MessageKey

  2. EntryType is "SEL" then MessageId format will be ^0[xX](([a-fA-F]|[0-9]){2}){3}$

i.e. first byte is EventData1 second byte is EventData2 and third byte is EventData 3.

MessageArgs

Array

True

  1. This contains message arguments to be substituted into the message included or in the message looked up via a registry.

  2. Populated only for AuditLog, EventLog and MetricReportLog.

Link

Object

 
Contains references to other resources that are related to this resource.

Name

Type

Read only

Description

OemObject Refer to Resource Complex Types.
OriginOfConditionObjectTrue

  1. This is the URI of the resource that caused the log entry.

  2. Refer idRef in odata4.0.0.json.

OemLogEntryCode

String

True

  1. If the LogEntryCode type is OEM, this will contain the OEM-specific entry code.

  2. Northbound only support.

OemSensorType

String

True

  1. If the Sensor Type is OEM, this will contain the OEM-specific sensor type.

  2. Northbound only support.

Table 2. EntryCode Strings

Assert

Transition to Busy

Informational

Redundancy Degraded

Deassert

State Deasserted

Device Removed / Device Absent

Non-redundant:Sufficient Resources from Redundant

Lower Non-critical - going low

State Asserted

Device Inserted / Device Present

Non-redundant:Sufficient Resources from Insufficient Resources

Lower Non-critical - going high

Predictive Failure deasserted

Device Disabled

Non-redundant:Insufficient Resources

Lower Critical - going low

Predictive Failure asserted

Device Enabled

Redundancy Degraded from Fully Redundant

Lower Critical - going high

Limit Not Exceeded

Transition to Running

Redundancy Degraded from Nonredundant

Lower Non-recoverable - going low

Limit Exceeded

Transition to In Test

D0 Power State

Lower Non-recoverable - going high

Performance Met

Transition to Power Off

D1 Power State

Upper Non-critical - going low

Performance Lags

Transition to On Line

D2 Power State

Upper Non-critical - going high

Transition to OK

Transition to Off Line

D3 Power State

Upper Critical - going low

Transition to Non-Critical from OK

Transition to Off Duty

 

Upper Critical - going high

Transition to Critical from less severe

Transition to Degraded

 

Upper Non-recoverable - going low

Transition to Non-recoverable from less severe

Transition to Power Save

 

Upper Non-recoverable - going high

Transition to Critical from Nonrecoverable

Install Error

 

Transition to Idle

Transition to Non-recoverable

Fully Redundant

 

Transition to Active

Monitor

Redundancy Lost

 
Table 3. SensorType Strings

Platform Security Violation Attempt

Other Units-based Sensor

Microcontroller/Coprocessor

OEM

Temperature

Memory

Add-in Card

 

Voltage

Drive Slot/Bay

Chassis

 

Current

POST Memory Resize

ChipSet

 

Fan

System Firmware Progress

Other FRU

 

Physical Chassis Security

Event Logging Disabled

Management Subsystem Health

 

Processor

System Event

Battery

 

Power Supply / Converter

Critical Interrupt

Session Audit

 

PowerUnit

Button/Switch

Version Change

 

CoolingDevice

Module/Board

FRUState