gin-contrib/logger

Issues

• Default writer change to os.stderr causes incorrect log severity interpretation in Cloud platforms

  #107 opened 2 months ago by hloiseaufcms
  0

• Allow log-level by specific http-status-code

  #104 opened 3 months ago by nicolaspastorbueno-yape
  0

• Logging should go to `stderr` by default

  #100 opened 3 months ago by itaranto
  0

• logging value in gin.Context after gin handler finish

  #95 opened 4 months ago by laggu
  6

• log line accumulation JSON logging

  #78 opened a year ago by odise
  2

• #65 per-request allocation reduction destroys this module

  #68 opened a year ago by mgabeler-lee-6rs
  0

• Allow for a logging level to be set for specific routes

  #71 opened a year ago by goodevilgenius
  0

• 升级为v0.3.0后日志出现错乱

  #70 opened a year ago by jaronzheng
  0

• Allow to log path query params

  #60 opened a year ago by dmartinol
  0

• Allow to log the response and request body

  #58 opened 2 years ago by dmartinol
  0

• Allow to configure writers different from zerolog.ConsoleWriter

  #41 opened 2 years ago by pscheid92
  5

• Disable pretty print

  #21 opened 3 years ago by dsychin
  1

• Add gin context data to logger output

  #8 opened 4 years ago by stringy05
  3

• Replace *zerolog.Logger with Logger interface

  #13 opened 4 years ago by laojianzi
  1

• Rename the key "user-agent" to "user_agent"

  #9 opened 4 years ago by 0xjac
  0

• how to rotate by size and time

  #6 opened 4 years ago by programervn
  1

• Attaching a request id to the logger

  #7 opened 4 years ago by josegonzalez
  3

• Support skip path like /js* /css*

  #5 opened 5 years ago by sky126
  1

• About the next release

  #4 opened 5 years ago by obynio
  6

• Support skip path

  #1 opened 6 years ago by appleboy
  0