Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • scalability scalability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 270
    • Issues 270
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Infrastructure TeamGitLab Infrastructure Team
  • scalabilityscalability
  • Issues
  • #68
Closed
Open
Issue created Dec 02, 2019 by Bob Van Landuyt@reprazentMaintainer

Add context information to the structured logs for requests

After #9 (closed) is implemented, we keep track of context information in a request:

  • The user performing the request
  • The project / namespace to which the request is targeted.

We currently use this information to add this to the sidekiq logs. But we could also include this information when writing to the production_json.log for rails requests by adding this to the lograge initializer.

To add this information to API requests, we could add an extra logger for Grape that includes this information.

Edited Dec 09, 2019 by Bob Van Landuyt
Assignee
Assign to
Time tracking