Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !946

Merged
Created Mar 24, 2021 by Jérome Perrin@jeromeOwner

software/erp5: include timestamp in haproxy error log

  • Overview 5
  • Commits 1
  • Pipelines 1
  • Changes 3

Haproxy log errors for events like when all backends from a family fail the health check, it is helpful for investigations to have a timestamp in this log.

We were using ActionFileDefaultTemplate so that access logs use standard "combined"-like format, we change so that this apply only to the access log, so that error log have the default "timestamp hostname process[pid] message" format.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix/haproxy-timestamp
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7