Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • replace-reopen
  • update-to-go-1-21-newer-go-mod
  • ashmckenzie/disable-gitaly-backwards-compat
  • refactor/remove-compat
  • go-mod-1.18
  • kassio/test-pages-backword-compatibility
  • mk-request-context-fields
  • 40-logging-roundtripper
  • ash2k/1.17-test
  • secure-archive-utilities
  • dependency-scanning
  • extend-examples
  • jarv-master-patch-93716
  • log-context-metadata-from-upstream
  • enable-pipelines-for-merge-requests
  • tracing-exclude-liveness-readiness
  • client-identity
  • reviewer-process
  • opentelemetry
  • v1.22.0
  • v1.21.2
  • v1.21.1
  • v1.21.0
  • v1.20.0
  • v1.19.0
  • v1.18.0
  • v1.17.0
  • v1.16.1
  • v1.16.0
  • v1.15.0
  • v1.14.0
  • v1.13.0
  • v1.12.0
  • v1.11.0
  • v1.10.0
  • v1.9.0
  • v1.8.0
  • v1.7.0
  • v1.6.0
40 results

mksyscall.go

  • Andrew Newdigate's avatar
    5a01133e
    Adds labkit logging package · 5a01133e
    Andrew Newdigate authored
    
    Unlike some of the other functionality provided by Logkit,
    the logging functionality does not wrap an underlying log provider.
    
    Why not? Because, in a past life, I worked as a Java developer and
    therefore understand that log wrappers will bring you nothing but pain
    and unhappiness.
    
    Instead of being a log wrapper, this functionality encourages
    applications to use logrus. Logrus is already widely used in GitLab.
    
    What benefit does this functionality add:
    * Consistent configuration of logrus
    * Importantly, this functionality allows labkit itself to write logs.
      * This will allow us to add better logging, as well as standardised
        access loggers, exception loggers etc
    
    Co-authored-by: default avatarZeger-Jan van de Weg <zegerjan@gitlab.com>
    5a01133e
    History
    Adds labkit logging package
    Andrew Newdigate authored
    
    Unlike some of the other functionality provided by Logkit,
    the logging functionality does not wrap an underlying log provider.
    
    Why not? Because, in a past life, I worked as a Java developer and
    therefore understand that log wrappers will bring you nothing but pain
    and unhappiness.
    
    Instead of being a log wrapper, this functionality encourages
    applications to use logrus. Logrus is already widely used in GitLab.
    
    What benefit does this functionality add:
    * Consistent configuration of logrus
    * Importantly, this functionality allows labkit itself to write logs.
      * This will allow us to add better logging, as well as standardised
        access loggers, exception loggers etc
    
    Co-authored-by: default avatarZeger-Jan van de Weg <zegerjan@gitlab.com>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.