Details

The server saves/sends (flushes) the accumulated metrics every often
(--flus-interval) to a persistent storage.
Carbon (from Graphite project)
is a very common backend for Statsd servers. Navdoon accepts multiple Graphite addresses (--flush-graphite)
so it can flush to multiple backends (all share the same interval).
Metrics can be flushed to standard output (--flush-stdout) to pipe to another
program, so it’s easy to integrate with any custom backend.

Logging can be helpful or can be wasteful, depending on the deployment and the usage of the application.
Navdoon provides detailed configuration on logging, so you can chose what will be logged (--log-level)
and how to log, send logs to syslog (--log-syslog), to a file (--log-file) or standard error
(--log-stderr) to be piped to another program.

While not claiming to be the fastest, good performance is considered in the design.
Navdoon uses threads for each collector and flush backend.
Future versions will offer improved performance as it was not a priority
for the first releases.

Server supports reloading (on receiving SIGHUP), keeping current state of the metrics and last flush time.
So it’s possible to change collectors, flush destinations, logging, etc. on the configuration file while
the server is running, and then on sending a SIGHUP the server picks the new configuration.

Releases

Latest released version is 0.2.0 (released on 2016-10-10)

Previous released version was 0.1.1 (released on 2016-06-15)

See the CHANGELOG for more information about features provided by each release.

Requirements

Navdoon is written in Python, so running from source or installing it as a package,
requires a Python runtime (version 2.7+, latest versions of Python 3 is recommended).

The statsdmetrics Python module
is the only dependency to run navdoon.
However these Python modules are recommended on development/test environment:

Running from source

Before running from source, a few dependencies should be installed. Using a virtual
environment is suggested. (In this example we create a virtual environment
in the project source path, but you may chose a custom path like
~/.venvs/navdoon-py3)