|
|
Post by sunitha on Sept 30, 2021 9:57:35 GMT
The LogEntry schema has a property "Link" , which can give the "OriginOfCondition" of the specific LogEntry. It is explained as "This property shall contain a link to the resource that caused the log entry."
My question is : When there is a user triggered (manually initiated) dump on a system, can this property be used to map to the session url which initiated the dump ?
Example response data for GET /redfish/v1/Managers/<manager>/LogServices/<id>/Entries/<id>
{
...
...
"Links": {
"OriginOfCondition": "/redfish/v1/SessionService/Sessions/<sessionId>"
},
...
...
}
|
|
|
|
Post by mraineri on Sept 30, 2021 12:41:53 GMT
There is the likely problem that the session may no longer be valid, and the URI would be broken.
For a manual trigger of data collection, it's probably not necessary to use OriginOfCondition in this LogEntry resource. OriginOfCondition is more important when there's additional information that a client might need to collect, but in this case everything should be self-contained. But if it's important to show who invoked the operation, we might need to discuss this aspect further.
|
|
|
|
Post by sunitha on Sept 30, 2021 13:25:17 GMT
Thanks for the quick answer mraineri . Yes. we have a use-case where we need to tie-up the LogEntry to the user who asked for it. Is there any other way to tag these with the current schema? |
|
|
|
Post by mraineri on Sept 30, 2021 15:04:33 GMT
Not at this time. One thought that comes to mind is to use OriginOfCondition to point to a ManagerAccount resource, but this doesn't work well with user accounts that come from an external account provider (like LDAP). Plus pointing to a ManagerAccount may be considered information leakage if a lower privilege account is reading logs.
|
|
|
|
Post by sunitha on Oct 4, 2021 14:07:15 GMT
mraineri Would redfish be interested in adding "InitiatedBy"/"CreatedBy" as an optional parameter at the LogEntry schema? Basically this can be used for a user initiated LogEntry (say user initiated dump) to give out the data as who triggered this.
|
|
|
|
Post by jautor on Oct 4, 2021 19:30:16 GMT
mraineri Would redfish be interested in adding "InitiatedBy"/"CreatedBy" as an optional parameter at the LogEntry schema? Basically this can be used for a user initiated LogEntry (say user initiated dump) to give out the data as who triggered this.
I think that is an interesting point that we should consider. Certainly for some types of logs (Audit, for example), the "who caused this entry" is an important piece of information.
|
|
|
|
Post by sunitha on Oct 5, 2021 13:05:22 GMT
Sounds good Jeff. Thank you.
|
|
