Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 147
    • Issues 147
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Merge requests
  • !1779

Open
Created Jun 09, 2022 by Igor Ponomarev@igo95862Contributor
  • Report abuse
Report abuse

Draft: Introduce lava database profiling logger

  • Overview 0
  • Commits 1
  • Changes 2

It tracks time in nanoseconds for each query and the lava stack which made the query.

Only activated if lava_server.dbtrace logger is set to DEBUG.

Example LOGGING configuration to activate:

"lava_server.dbtrace": {
    "handlers": ["console"],
    "level": "DEBUG",
    "propagate": False,
},

Mostly useful with the new JSON formatter to process logs.

Unless lava_server.dbtrace logger is set to DEBUG there is no performance impact.

Edited Jun 09, 2022 by Igor Ponomarev
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: trace-database-logger