This package adds support for TraceView performance instrumentation in Plone
Project description
Traceview for Plone
The collective.traceview package adds support for Traceview (aka Tracelytics) to Plone.
Traceview times the full request from the browser through frontend servers to application servers. collective.traceview gives you insight into Zope/Plone internals and adds these layers to Traceview:
Zope http server
Zope publisher
ZODB
Portal Transforms
Outbound calls to e.g. webservices
Portal Catalog searches
It also adds tags to the HTML header and footer to instrument Traceview Real User Monitoring (RUM), so you’ll get metrics about user network connectivity and how long time your site takes to render inside the browsers of the real users.
Requirements
You need a Traceview account, Traceview installed on the Plone server. And then the Traceview Python oboe library must be installed with the same Python that runs Plone.
collective.traceview has been tested with Plone 4.
How to install
Update your buildout.cfg file:
Add package in develop mode
auto-checkout = collective.traceview
Add oboe and collective.traceview to the list of eggs to install
[instance] ... eggs = ... collective.traceview oboe
Get package from collective sources (or create your own GitHub fork)
[sources] ... collective.traceview = git https://github.com/collective/collective.traceview.git
Re-run buildout, e.g. with:
$ ./bin/buildout
Contributors
- Note: place names and roles of the people who contribute to this package
in this file, one to a line, like so:
Joe Schmoe, Original Author
Bob Slob, contributed monkey patches
Jane Main, wrote flibberty module
Bo Simonsen, misc changes
Changelog
1.1-dev - (unreleased)
Fixed CHANGES.txt for better formatting and to reflect latest release [alecghica]
1.0 - (2013-05-21)
Initial public development release [bosim]
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
