zperfmetrics 1.0b3

Perfmetrics configuration for Zope and Plone

zperfmetrics works like and depends on perfmetrics, additional it:

• offers a ZConfig configuration for the statsd,

• uses the current requests path in the statd dotted path prefix,

• also provides a patch to measure plone.app.theming for diazo compile and diazo transform if Plone is available,

Installation

First get your statsd configured properly. This is out of scope of this module.

Depend on this module in your packages setup.py.

Given you use zc.builodut to set up your Zope2 or Plone, add to your [instance] section or the section with recipe = plone.recipe.zope2instance the lines:

[instance01]
recipe = plone.recipe.zope2instance
...
zope-conf-imports =
    zperfmetrics
zope-conf-additional =
    <perfmetrics>
        uri statsd://localhost:8125
        before MyFancyProject
        hostname on
        virtualhost on
        after ${:_buildout_section_name_}
    </perfmetrics>
...

Given this runs on a host called w-plone1, this will result in a prefix MyFancyProject.w-plone1.instance01.

uri

Full URI of statd.

before

Prefix path before the hostname.

hostname

Get hostname and insert into prefix. (Boolean: on or off)

virtualhost

Get virtualhost and use in ZPerfmetrics after the static prefix. (Boolean: on or off)

after

Prefix path after the hostname.

Usage

You need to decorate your code or use the with statement to measure a code block.

Usage:

from zperfmetrics import ZMetric
from zperfmetrics import zmetric
from zperfmetrics import zmetricmethod

@zmetric
def some_function():
    # whole functions timing and call counts will be measured
    pass

@ZMetric(stat='a_custom_prefix')
def some_other_function():
    # set a custom prefix instead of module path and fucntion name.
    pass

class Foo(object):

    @zmetricmethod
    def some_method(self):
        # whole methods timing and call counts will be measured
        pass

    @ZMetric(method=True, timing=False):
    def some_counted_method(self):
        # whole methods number of calls will be measured, but no times
        pass

    @ZMetric(method=True, count=False):
    def some_timed_method(self):
        # whole methods timing be measured, but no counts
        pass

    def some_method_partly_measured(self):
        # do something here you dont want to measure
        with ZMetric(stat='part_of_other_method_time'):
            # do something to measure
            # call counts and timing will be measured
            pass
        # do something here you dont want to measure

    @ZMetric(method=True, rate=0.5):
    def some_random_recorded_method(self):
        # randomly record 50% of the calls.
        pass

Request Lifecycle Integration

All ZPerfmetrics with a request passed in are considered to be under the request_lifecycle section.

All metrics in here are build like: $PREFIX.request_lifecycle.[$VIRTUAL_HOST].$PATH.*.

Statd, Graphite & Grafana in Docker

Setting up Statsd, Graphite and Grafana can be complex. For local testing - but also for production environments - firing up some docker containers comes in handy.

A very minimal version of such a Statd, Graphite & Grafana in Docker setup (original) helps getting things initially up and running. Install Docker and install docker-compose (just pip install docker-compose), then just clone the repository and in its docker directory run docker-compose up -d.

Let Zperfmetrics point to uri statsd://localhost:8125 and collect some data. Open Grafana in your browser at http://localhost:3000.

Go first to Grafana Getting Started, the 10 minute video really helps to find the hidden part of its UI.

Source Code

The sources are in a GIT DVCS with its main branches at github.

We’d be happy to see many branches, forks and pull-requests to make zperfmetrics even better.

Contributors

• Jens W. Klein <jens@bluedynamics.com>

• Zalán Somogyváry

History

License

Copyright (c) 2016, BlueDynamics Alliance, Austria, Germany, Switzerland All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of the BlueDynamics Alliance nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.