|
Post by yaojun26 on Nov 19, 2021 18:14:01 GMT
There are various types of events we need to monitor and log. I think the LogService is the good place to represent the events.
What's the relationship between a LogService and an event type?
For example, if we want to represent three types of events: CPU error, memory error, machine reboot.
Should I put them to three different LogServices like: * /redfish/v1/Systems/{ComputerSystemId}/LogServices/CpuError/Entries/{LogEntryId} * /redfish/v1/Systems/{ComputerSystemId}/LogServices/MemoryError/Entries/{LogEntryId} * /redfish/v1/Systems/{ComputerSystemId}/LogServices/Reboot/Entries/{LogEntryId}
|
|
|
Post by mraineri on Nov 19, 2021 20:17:46 GMT
Yes, you can technically break it out into multiple log services between the different types of events. However, I don't think most users will find this very useful. Most folks I talk to like to see events like this in a single, chronological log so they can step through events that happen over time.
If a client really needs to inspect classes of events separately, they can perform $filter on the LogEntryCollection.
|
|