Python
How to setup recording & monitoring for Python applications
RevDeBug supplies a ready Docker container based on vanilla Debian Buster docker images that can be used as a drop-in replacement for your own microservices.
The Docker image can be used also to run a separate Python interpreter process to run applications outside the container as well.
Supported Python runtime versions
3.8.13
docker.revdebug.com/python-revdebug:3.8
3.9.13
docker.revdebug.com/python-revdebug:3.9
3.10.5
docker.revdebug.com/python-revdebug:3.10
Configuration using a configuration file
The RevDeBug Python configuration is first read from an optional revdebug.cfg file in the current working directory of your application. Those settings can be set or overridden through environment variables.
Then the script base directory is checked for the file again and if it is present it is read and overrides any settings from the previous file (if one was read). Finally, environment variables are checked and override anything which may have come from a config file.
The config file options (case insensitive) are as follows:
You can read more about configuration options here
Minimal set of configuration required
REVDEBUG_SOLUTION
- application or project name.REVDEBUG_RELEASE
- should be set to a git hash of a current release commit.REVDEBUG_APPLICATIONS_HOST
- fully qualified domain name or IP address of RevDeBug Server.REVDEBUG_MODE
- should be set toOnEvent
for on error recording, other possible values areOff
(still can gather APM metrics, see setting below) orContinuous
for live from start to program stop recording.REVDEBUG_APM
- should be set to1
for application performance metrics collection or0
to disable.
Last updated