• Andrew Newdigate's avatar
    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: 's avatarZeger-Jan van de Weg <zegerjan@gitlab.com>
    5a01133e
Name
Last commit
Last update
..
connstr Loading commit data...
correlation Loading commit data...
grpc Loading commit data...
impl Loading commit data...
doc.go Loading commit data...
env_extractor.go Loading commit data...
env_extractor_option.go Loading commit data...
env_extractor_test.go Loading commit data...
env_injector.go Loading commit data...
env_injector_option.go Loading commit data...
env_injector_test.go Loading commit data...
errors.go Loading commit data...
examples_test.go Loading commit data...
inbound_http.go Loading commit data...
inbound_http_options.go Loading commit data...
initialization.go Loading commit data...
initialization_options.go Loading commit data...
outbound_http.go Loading commit data...
outbound_http_options.go Loading commit data...