Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.cmdline
beat.cmdline
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.cmdlinebeat.cmdline
  • Issues
  • #14

Closed
Open
Opened Aug 25, 2017 by Jaden DIEFENBAUGH@jdiefenbaugh
  • Report abuse
  • New issue
Report abuse New issue

More detailed logging at various verbosity levels

Right now, the various verbosity levels don't provide much more information than not passing a verbosity level at all. Some ideas:

  • More cache information
    • Logging the block & its cache would be especially useful
  • More statistics (especially for the local executor)
  • Printing output of every block, not just the analyser
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
enhancement
Assign labels
  • View project labels
Reference: beat/beat.cmdline#14