https://bugzilla.redhat.com/show_bug.cgi?id=1789161

            Bug ID: 1789161
           Summary: Review Request: cadvisor - Analyzes resource usage and
                    performance characteristics of running containers
           Product: Fedora
           Version: rawhide
            Status: NEW
         Component: Package Review
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected]
  Target Milestone: ---
    Classification: Fedora




Spec URL: https://eclipseo.fedorapeople.org//cadvisor.spec
SRPM URL:
https://eclipseo.fedorapeople.org//cadvisor-0.33.1-4.20190708git2ccad4b.fc32.src.rpm

Description:

cAdvisor (Container Advisor) provides container users an understanding of the
resource usage and performance characteristics of their running containers. It
is a running daemon that collects, aggregates, processes, and exports
information about running containers. Specifically, for each container it keeps
resource isolation parameters, historical resource usage, histograms of
complete
historical resource usage and network statistics. This data is exported by
container and machine-wide.

cAdvisor has native support for Docker containers and should support just about
any other container type out of the box. We strive for support across the board
so feel free to open an issue if that is not the case. cAdvisor's container
abstraction is based on lmctfy's so containers are inherently nested
hierarchically.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to