You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We would like to use filesystem modification events for audit logging on our BeeGFS storage, but without a UID in the events, this is not possible.
Describe the solution you'd like
Add the UID of the user carrying out the operation to the filesystem modification events. Since this is just adding a field to the JSON, it's backwards-compatible. The UID seems to be included in all NetMessage messages to the metadata server, so the information is readily available with getMsgHeaderUserID().
It seems that there's only 10 locations in the code where an operation is logged, for example:
Running auditd on each compute node and collecting logs. However, it's not as reliable or flexible as an approach based on filesystem modification events.
Additional context
None.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We would like to use filesystem modification events for audit logging on our BeeGFS storage, but without a UID in the events, this is not possible.
Describe the solution you'd like
Add the UID of the user carrying out the operation to the filesystem modification events. Since this is just adding a field to the JSON, it's backwards-compatible. The UID seems to be included in all
NetMessage
messages to the metadata server, so the information is readily available withgetMsgHeaderUserID()
.It seems that there's only 10 locations in the code where an operation is logged, for example:
beegfs/meta/source/net/message/session/opening/OpenFileMsgEx.cpp
Line 81 in 2bb9244
Describe alternatives you've considered
Running
auditd
on each compute node and collecting logs. However, it's not as reliable or flexible as an approach based on filesystem modification events.Additional context
None.
The text was updated successfully, but these errors were encountered: