Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 914
    • Issues 914
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #1586

Closed
Open
Opened Feb 11, 2020 by eileen@eileen🎱Owner

Add ? option? to NOT log to civicrm_log when logging is enabled

I was under the impression that we didn't use the civicrm_log table when we enable logging - certainly it becomes inaccessible through the UI. However, I have discovered that the table has swollen to 32 GB and that new entries are regularly logged.

I feel like this duplicates the function of logging / is kind of 'logging-lite' and I thought for that reason we didn't do it. However, I realise changing it might cause issues. All I can think of is a setting to not log o civicrm_log if logging is enabled.

@seamuslee @pfigel @jitendra any thoughts?

Edited Feb 11, 2020 by eileen
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1586