Creating Additional Dashboards

[mengelsen]

If I create additional Dashboards or Members (within the InfluxDB UI) can those changes be preserved if the Vuegraf and InfluxDB containers gets removed and recreated?

[jertel]

As long as you followed the Vuegraf installation guide, and specifically, bound a persistent directory into the InfluxDB container for the permanent storage of InfluxDB data, then yes, you can destroy the containers and recreate them without losing data.

[jertel]

They are stored in sqlite. Remember during the installation guide that you imported that json file into InfluxDB.

[mengelsen]

That all makes perfect sense. Just to be on the safe side, I also found a way to export my dashboard to a .json file.

Side Note: would you consider updating your Installation Instructions? There are (2) references to docker run.
Can you please append the following launch argument to the docker run command:
-restart always
I think others will find it helpful if their InfluxDB and Vuegraf containers auto-start on boot.

[mengelsen]

Updated docker run commands:

sudo docker run -d -v /home/<<username_HERE>>/influxdb2:/var/lib/influxdb2 -p 8086:8086 -e INFLUXD_SESSION_LENGTH=432000 --restart always --name influxdb influxdb
sudo docker run --name vuegraf -d -v /home/<<username_HERE>>/vuegraf:/opt/vuegraf/conf jertel/vuegraf --restart always

[mengelsen]

The --restart argument works w/o issue on influxdb. But vuegraf doesn't currently accept --restart

pi@raspberrypi:~ $ sudo docker logs vuegraf
usage: vuegraf.py [-h] [-v] [-d] [--historydays HISTORYDAYS] [--resetdatabase]
                  configFilename
vuegraf.py: error: unrecognized arguments: --restart

[jertel]

I could, but this is getting more into productionalizing a server, and configuring the container to restart any time it crashes or the server reboots is just a small piece of what's required to do this correctly.

Perhaps a note at the end of the getting started guide that reminds them there are additional steps necessary for making this configuration fault tolerant, such as configuring the container to always restart, backing up their InfluxDB on a frequent basis, log rollover management, OS alerts to an admin when InfluxDB crashes, checking for low disk space on the host, setting up calendar reminders for host OS updates and associated kernel reboots, updating Vuegraf and Influx on a schedule, etc.

Also, move the --restart always after the docker run words to avoid the Vuegraf error you pasted.