Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D Deimos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • performance
  • storage
  • Deimos
  • Issues
  • #57
Closed
Open
Issue created Apr 22, 2020 by Sophie Wenzel-Teuber@sophie.wenzel-teuberMaintainer

Add logging

Different kinds of log files might be set up on the server.

One possibility is to add general log files on the server level for all request that come in.

Another is the S3 approach where logging can be activated on a bucket level ( dependent on issue #53 (closed) ) and then all executed tasks on that bucket and its objects are logged (who does what and when). Documentation for this can be found here: https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerLogs.html

The main difference is that the user has access to the second type of logs, where in the first case only the server maintainer can access them.

Assignee
Assign to
Time tracking