# Handler Status

## Presentation

When status feature is activated, Handlers and portal will collect statistics and save them in their local cache. This means that if several Handlers are deployed, each will manage its own statistics.

This page can be browsed for example by MRTG using the MRTG monitoring script.

The statistics are collected trough a daemon launched by the Handler. It can be seen in system processes, for example:

    perl -MLemonldap::NG::Handler::Status -I/etc/perl -I/usr/local/lib/perl/5.10.1 -I/usr/local/share/perl/5.10.1 -I/usr/lib/perl5 -I/usr/share/perl5 -I/usr/lib/perl/5.10 -I/usr/share/perl/5.10 -I/usr/local/lib/site_perl -I. -I/etc/apache2 -e &Lemonldap::NG::Handler::Status::run(Cache::FileCache,{?          'cache_depth' => 5,?          'cache_root' => '/tmp',?          'directory_umask' => '007',?          'default_expires_in' => 600,?          'namespace' => 'MyNamespace'?        }?);

Statistics are displayed when calling the status path on an Handler (for example: http://test1.example.com/status).

Example of status page:

## Configuration

### Apache

You need to give access to status path in the Handler Apache configuration:

        # Uncomment this to activate status module
        <Location /status>
            Order deny,allow
            Allow from 127.0.0.0/8
            PerlHeaderParserHandler Lemonldap::NG::Handler->status
        </Location>

Then restart Apache.

You should change the `Allow` directive to match administration IP, or use another Apache protection mean.

### LemonLDAP::NG

Edit `lemonldap-ng.ini`, and activate status in the `handler` section:

    [handler]
    # Set status to 1 if you want to have the report of activity (used for
    # example to inform MRTG)
    status = 1

Then restart Apache.