Once you have successfully installed the Flask-MonitoringDashboard using the instructions from the installation page, you can use the advanced features by correctly configuring the Dashboard.

Using a configuration file

You can use a single configuration file for all options below. This is explained in the following section. In order to configure the Dashboard with a configuration-file, you can use the following function:

dashboard.config.init_from(file='/<path to file>/config.cfg')

Your app then becomes:

from flask import Flask
import flask_monitoringdashboard as dashboard

app = Flask(__name__)
dashboard.config.init_from(file='/<path to file>/config.cfg')
# Make sure that you first configure the dashboard, before binding it to your Flask application

def index():
    return 'Hello World!'

if __name__ == '__main__':

Instead of having a hard-coded string containing the location of the config file in the code above, it is also possible to define an environment variable that specifies the location of this config file. The line should then be:


This will configure the Dashboard based on the file provided in the environment variable called FLASK_MONITORING_DASHBOARD_CONFIG.

The content of the configuration file

Once the setup is complete, a configuration file (e.g. ‘config.cfg’) should be set next to the python file that contains the entry point of the app. The following properties can be configured:

GIT=/<path to your project>/.git/


DATABASE=sqlite:////<path to your project>/dashboard.db


As can be seen above, the configuration is split into 4 headers:


  • APP_VERSION: The version of the application that you use. Updating the version allows seeing the changes in the execution time of requests over multiple versions.
  • GIT: Since updating the version in the configuration-file when updating code isn’t very convenient, another way is to provide the location of the git-folder. From the git-folder, the version is automatically retrieved by reading the commit-id (hashed value). The specified value is the location to the git-folder. This is relative to the configuration-file.
  • CUSTOM_LINK: The Dashboard can be visited at localhost:5000/{{CUSTOM_LINK}}.
  • MONITOR_LEVEL: The level for monitoring your endpoints. The default value is 3. For more information, see the Overview page of the Dashboard.
  • OUTLIER_DETECTION_CONSTANT: When the execution time is greater than \(constant * average\), extra information is logged into the database. A default value for this variable is \(2.5\).
  • SAMPLING_PERIOD: Time between two profiler-samples. The time must be specified in ms. If this value is not set, the profiler monitors continuously.
  • ENABLE_LOGGING: Boolean if you want additional logs to be printed to the console. Default value is False.


  • USERNAME and PASSWORD: Must be used for logging into the Dashboard. Both are required.
  • SECURITY_TOKEN: The token that is used for exporting the data to other services. If you leave this unchanged, any service is able to retrieve the data from the database.


  • TABLE_PREFIX: A prefix to every table that the Flask-MonitoringDashboard uses, to ensure that there are no conflicts with the other tables, that are specified by the user of the dashboard.
  • DATABASE: Suppose you have multiple projects that you’re working on and want to separate the results. Then you can specify different database_names, such that the result of each project is stored in its own database.


  • TIMEZONE: The timezone for converting a UTC timestamp to a local timestamp. For a list of all timezones, use the following:

    import pytz  # pip install pytz

    The dashboard saves the time of every request by default in a UTC-timestamp. However, if you want to display it in a local timestamp, you need this property.

  • COLORS: The endpoints are automatically hashed into a color. However, if you want to specify a different color for an endpoint, you can set this variable. It must be a dictionary with the endpoint-name as a key, and a list of length 3 with the RGB-values. For example:


What have you configured?

We’ve shown a bunch of configuration settings, but what features are now supported in your Flask application and how are they related to the config options? Have a look at the detailed functionality page to find the answer.