Package: dsinfluxlogger
Log PubSubDataMessages (see datastreamcorelib) to InfluxDB, this is a pretty quick and dirty implementation
and definitely not optimal. Supports only InfluxDB < 2.0 (ie 1.8) due to aioinflux not supporting 2.0.For optimal write performance we should add a plugin system that allows
one to convert the payload from the PubSubDataMessages into line-protocol decorated
custom classeshttps://aioinflux.readthedocs.io/en/stable/usage.html#writing-user-defined-class-objectsThe quick-and-dirty optimization is to batch writes into pandas dataframes, which has the not
insignificant drawback of adding pandas/numpy to our requirements.DockerFor more controlled deployments and to get rid of “works on my computer” -syndrome, we always
make sure our software works under docker.It’s also a quick way to get started with a standard development environment.SSH agent forwardingWe needbuildkit:export DOCKER_BUILDKIT=1And also the exact way for forwarding agent to running instance is different on OSX:export DOCKER_SSHAGENT="-v /run/host-services/ssh-auth.sock:/run/host-services/ssh-auth.sock -e SSH_AUTH_SOCK=/run/host-services/ssh-auth.sock"and Linux:export DOCKER_SSHAGENT="-v $SSH_AUTH_SOCK:$SSH_AUTH_SOCK -e SSH_AUTH_SOCK"Creating a development containerBuild image, create container and start it:docker build --ssh default --target devel_shell -t dsinfluxlogger:devel_shell .
docker create --name dsinfluxlogger_devel -p 58770:58770 -v `pwd`":/app" -it -v /tmp:/tmp `echo $DOCKER_SSHAGENT` dsinfluxlogger:devel_shell
docker start -i dsinfluxlogger_develpre-commit considerationsIf working in Docker instead of native env you need to run the pre-commit checks in docker too:docker exec -i dsinfluxlogger_devel /bin/bash -c "pre-commit install"
docker exec -i dsinfluxlogger_devel /bin/bash -c "pre-commit run --all-files"You need to have the container running, see above. Or alternatively use the docker run syntax but using
the running container is faster:docker run -it --rm -v `pwd`":/app" dsinfluxlogger:devel_shell -c "pre-commit run --all-files"Test suiteYou can use the devel shell to run py.test when doing development, for CI use
the “tox” target in the Dockerfile:docker build --ssh default --target tox -t dsinfluxlogger:tox .
docker run -it --rm -v `pwd`":/app" `echo $DOCKER_SSHAGENT` dsinfluxlogger:toxProduction dockerThere’s a “production” target as well for running the application (change “myconfig.toml” for config file):docker build --ssh default --target production -t dsinfluxlogger:latest .
docker run -it --name dsinfluxlogger -v myconfig.toml:/app/config.toml -p 58770:58770 -it -v /tmp:/tmp `echo $DOCKER_SSHAGENT` dsinfluxlogger:latestLocal DevelopmentTLDR:Create and activate a Python 3.8 virtualenv (assuming virtualenvwrapper):mkvirtualenv -p `which python3.8` my_virtualenvchange to a branch:git checkout -b my_branchinstall Poetry:https://python-poetry.org/docs/#installationInstall project deps and pre-commit hooks:poetry install
pre-commit install
pre-commit run --all-filesReady to go, try the following:dsinfluxlogger --defaultconfig >config.toml
dsinfluxlogger -vv config.tomlRemember to activate your virtualenv whenever working on the repo, this is needed
because pylint and mypy pre-commit hooks use the “system” python for now (because reasons).Running “pre-commit run –all-files” and “py.test -v” regularly during development and
especially before committing will save you some headache.