Bug 1248178 - Review Request: lttnganalyses - LTTng trace analysis tools
Review Request: lttnganalyses - LTTng trace analysis tools
Status: NEW
Product: Fedora
Classification: Fedora
Component: Package Review (Show other bugs)
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-07-29 15:31 EDT by Michael Jeanson
Modified: 2015-07-29 15:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Jeanson 2015-07-29 15:31:44 EDT
Spec URL: http://www.multivax.ca/SRPMS/lttnganalyses.spec
SRPM URL: http://www.multivax.ca/SRPMS/lttnganalyses-0.3.0-1.fc24.src.rpm
This package contains various tools to analyse LTTng kernel traces and extract
monitoring data and metrics. As opposed to other diagnostic or monitoring
solutions, this approach is designed to allow users to record their system's
activity with a low overhead, wait for a problem to occur and then diagnose
its cause offline.
Fedora Account System Username: mjeanson

This is my first package in Fedora and as such I will need a sponsor, once I am a member of the packager group I plan to co-maintain the LTTng related packages, I have already contributed patches to the actual maintainers. I work at Efficios, the upstream maintainer of the LTTng project. 

Here is a successful koji build of the package : http://koji.fedoraproject.org/koji/taskinfo?taskID=10531571

This package depends on the python3 bindings of the babeltrace library which are only packaged in rawhide currently, for convenience here is a copr repo with the packages currently being pushed to rawhide : https://copr.fedoraproject.org/coprs/mjeanson/lttng-2.6/

Note You need to log in before you can comment on or make changes to this bug.