Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Monitoring Plugins Collection
Monitoring Plugins Collection
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Linuxfabrik
  • Monitoring Plugins CollectionMonitoring Plugins Collection
  • Issues
  • #117

Closed
Open
Created Aug 18, 2020 by Markus Frei@markus.freiOwner

procs: Improve Output by aggregating multiple procs

Imagine this output: 162 tasks, 127 sleeping, 34 zombies (python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2, python2), 1 running (rcu_sched)

Make it like so: 162 tasks, 127 sleeping, 34 zombies (34x python2), 1 running (rcu_sched)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None