You are reading temBoard 7 documentation. You may want to contribute to latest version of the documentation. Use Read The Docs version selector or go to latest documentation.

Reporting an Issue & Submitting a Patch

We use the dalibo/temboard project to track issue and review contributions. Fork the main repository and open a PR against master as usual.

Development Environment Setup

You can quickly set up a dev env with virtualenv and Docker Compose. Running development version of UI and agent requires two shells, one for the UI and one for the agent.

Get temBoard UI and agent sources:

$ git clone --branch v7 --recursive
$ cd temboard/
$ git clone --recursive agent/

Then, create a virtualenv for Python3.6+ or Python2.7, activate it. Then install temBoard and pull docker images:

$ pip install -e . -r requirements-dev.txt
$ docker-compose pull

Then, bootstrap development with make devenv.

$ make devenv
2020-03-24 17:09:05,937 [30557] [migrator        ]  INFO: Database is up to date.
Initialized role temboard and database temboard.
docker-compose up -d
temboard_repository_1 is up-to-date
Creating temboard_instance_1 ... done
Creating temboard_agent_1    ... done

$ temboard --debug
2020-03-24 17:11:55,997 [ 3551] [temboardui      ]  INFO: Starting temBoard 4.0+master on Debian GNU/Linux 10 (buster).
2020-03-24 17:11:56,015 [ 3551] [temboardui      ]  INFO: Serving temboardui on

Go to to access temBoard running with your code!

You now need to run an agent and register it in UI. Open a second shell for managing the agent and execute the following commands.

$ docker-compose exec agent0 /bin/bash
root@91cd7e12ac3e:/var/lib/temboard-agent# sudo -u postgres hupper -m temboardagent.scripts.agent
 INFO: Starting temboard-agent 8.0.dev0.
 INFO: Found config file /etc/temboard-agent/temboard-agent.conf.
2020-08-11 14:29:45,834 [ 3769] [app             ] DEBUG: Looking for plugin activity.

Now register the agent in UI, using host, port 2345 and key key_for_agent. The monitored Postgres instance is named

Beware that two Postgres instances are set up with replication. The primary instance may be either postgres0 or postgres1. See below for details.

Execute unit tests

Use pytest to run unit tests:

$ pytest tests/unit
==== 31 passed, 10 warnings in 1.10 seconds ======

Execute func tests

Go to tests/func and run docker-compose:

$ cd tests/func
tests/func/$ docker-compose up --force-recreate --always-recreate-deps --renew-anon-volumes --abort-on-container-exit ui

Functionnal tests are executed outside temboard process. UI is installed and registered using regular tools : pip, dpkg or yum,, etc. A real Postgres database is set up for the repository

Tests are written in Python with pytest. Tests use selenium to communicate with the UI.

For development purpose, a docker-compose.yml file describe the setup to execute functionnal tests almost like on Circle CI. The main entry point is tests/func/ which is responsible to install temboard, configure it and call pytest with selenium parameters.

On failure, the main container, named ui, wait for you to enter it and debug. Project tree is mounted at /workspace.

tests/func/$ docker-compose exec ui /bin/bash
[root@ccb2ec0d78cb workspace]# tests/func/ --pdb -x

Testing with Postgres replication

Two postgres instance are up with replication. You can execute a second agent for it likewise:

$ docker-compose exec agent1 /bin/bash
root@91cd7e12ac3e:/var/lib/temboard-agent# sudo -u postgres hupper -m temboardagent.scripts.agent
 INFO: Starting temboard-agent 8.0.dev0.
 INFO: Found config file /etc/temboard-agent/temboard-agent.conf.
2022-01-11 10:12:55,130 [ 1568] [app             ] DEBUG: Looking for plugin activity.

bash history is shared amongst these two containers.

In UI, register the second agent with address, port 2346 instead of 2345, with the same key key_for_agent. The instance FQDN is

The script docker/ triggers a switchover between the two postgres instances. Executing docker/ one more time restore the original topology.

Editing Documentation

The documentation is written in markdown and built with mkdocs

$ mkdocs serve
INFO     -  Building documentation...
INFO     -  Cleaning site directory
INFO     -  The following pages exist in the docs directory, but are not included in the "nav" configuration:
INFO     -  Documentation built in 0.42 seconds
INFO     -  [16:21:24] Serving on

Go to to view the documentation. mkdocs serve has hot reload while you edit the documentation.

Throw your development environment

If you want to trash development env, use docker-compose down -v and restart from make devenv.

Entering Monitored PostgreSQL Instance with psql

Use the following command:

$ docker-compose exec agent0 sudo -iu postgres psql
psql (13.5 (Debian 13.5-0+deb11u1), server 14.1)
WARNING: psql major version 13, server major version 14.
         Some psql features might not work.
Type "help" for help.


Monitoring another version of PostgreSQL

You can change the version of the monitored PostgreSQL instance by overriding docker image in docker-compose.override.yml.

# file docker-compose.override.yml
version: "2.4"

    image: postgres:9.5-alpine

Now apply changes with make devenv. Docker-compose will recreate postgres and agent containers, thus you need to install and start the agent as documented above.


temBoard UI mainly relies on Bootstrap. The CSS files are compiled with SASS.

In case you want to contribute on the styles, first install the nodeJS dev dependencies:

npm install

Then you can either build a dist version of the css:

grunt sass:dist

Or build a dev version which will get updated each time you make a change in any of the .scss files:

grunt watch

Launching Multiple Agents

Default development environment instanciate a single PostgreSQL instance and it's temBoard agent. Root Makefile offers two targets to help testing bigger infrastructure :

  • make mass-agents loops from 2345 to 2400 and instanciate a PostgreSQL instance and an agent to monitor it. Each instanciation requires you to type y. This allows to throttle instanciations and to stop when enough instances are up.
  • make clean-agents trashes every existings instances from 2345 to 2400, without interaction. Agent are not unregistered!

Coding style

An .editorconfig file is included at the root of the repository configuring whitespace and charset handling in various programming language. The EditorConfig site links to plugins for various editors. See .editorconfig for a description of the conventions. Please stick to this conventions.

Python syntax must conform to flake8. Our CI checks new code with flake8.

Contribution Workflow

Fork the project, commit in a branch and open a new GithUb PR on

Building a snapshot

You can build a snapshot RPM like this:

$ make snapshot
$ make -C packaging/rpm build-rhel8

Releasing the Server

Releasing a new version of temBoard requires write access to master on main repository, PyPI project, Docker Hub repository and Dalibo Labs YUM and APT repositories.

For the tooling, you need Git 1.8+, a recent setuptools with wheel. For distribution packaging, see ad-hoc documentation in packaging/.

To release a new version:

  • Checkout release branch (like v2).
  • Choose the next version according to [PEP 440] (
  • Update temboardui/, without committing.
  • Generate and push commit and tag with make release.
  • Push Python egg to PyPI using make upload.
  • Build and upload RPM package with make -C packaging/rpm release.
  • Build and upload Debian package with make -C packaging/deb release.

Releasing the Agent

Releasing a new version of temBoard agent requires write access to master on main repository, PyPI project and Docker Hub repository.

For the tooling, you need Git 1.8+, a recent setuptools with wheel, and twine. For debian packaging, see below.

Please follow these steps:

  • Checkout the release branch, e.g. v2.
  • Choose the next version according to PEP 440 .
  • Update temboardagent/, without committing.
  • Generate commit and tag with make release.
  • Push Python egg to PyPI using make upload.
  • Build and push RPM packages using make -C packaging/rpm all push.
  • Build and push debian packages using make -C packaging/deb all push.

Other documentation for maintainers

Checkout the RPM packaging README for the agent: