Related to #2721 #2759

Overview

All actions related to Storage Lifecycle Policy should be logged within Security Logs for good traceability:

• Lifecycle Archiving rules
  • Lifecycle Rule creation
  • Lifecycle Rule changes
  • Lifecycle Rule deletion
  • Lifecycle Rule prolongation for specific path
  • Lifecycle Rule execution for specific path
• Lifecycle Restoring actions
  • Lifecycle restore action creation
  • Lifecycle restore action status update

Main concept points

• New security log 'topic' Storage Lifecycle should be introduced.
• Existed solution should be reused as much as possible.

Technical details

API server changes

While such events as:

• Lifecycle Archiving rules
  • Lifecycle Rule creation
  • Lifecycle Rule changes
  • Lifecycle Rule deletion
  • Lifecycle Rule prolongation for specific path
• Lifecycle Restoring actions
  • Lifecycle restore action creation

can be handled in API server and be appended to api security log,
only thing that we need to do here is to appropriately log all necessary events in api server code.

storage-lifecycle-service changes

To be able to process the next events:

• Lifecycle Archiving rules
  • Lifecycle Rule notification for specific path
  • Lifecycle Rule execution for specific path
• Lifecycle Restoring actions
  • Lifecycle restore action status update

We need to expand logging for such events along with providing a ways to collect such logs and push it to elasticsearch

In this case approach, that used for edge service could be good match:

• Collect all special logs to separate location
• use elastic filebeat agent to automatically push it to elastic