Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • CTA CTA
  • 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 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ctacta
  • CTACTA
  • Issues
  • #225
Closed
Open
Issue created Nov 25, 2022 by Joao Afonso@afonsoOwner

Re-evaluate the priorities of the most commonly issued CTA and EOS-CTA logs

As explained in https://gitlab.cern.ch/cta/operations/-/issues/921, some of the CTA/EOS-CTA instances are producing an extremely high amount of logs that fill all the allocated disk space.

We need to confirm which log entries are causing this, and evaluate if there is any way to decrease their occurrences (either by reducing the priority or other mechanisms).

Edited Nov 25, 2022 by Joao Afonso
Assignee
Assign to
Time tracking