Jump to content

atribe

Community Developer
  • Content Count

    116
  • Joined

  • Last visited

Everything posted by atribe

  1. You can use this tool to view and manage influxdb database https://github.com/CymaticLabs/InfluxDBStudio/releases I use it and like it better than the command line.
  2. Probably the cost of switching the repo. See the bottom left of you screenshot? Libray/telegraf. You customized it. You might be able to go into the file system where that template info is stored and put the icon there.
  3. Use environment variables in the docker setup to set all of these. See the docs: https://grafana.com/docs/grafana/latest/installation/configuration/#configure-with-environment-variables
  4. Do you have the WATTS variable set in the apcupsd-influxdb-exporter docker?
  5. If you can't find it, just add it. [[inputs.apcupsd]] # A list of running apcupsd server to connect to. # If not provided will default to tcp://127.0.0.1:3551 servers = ["tcp://127.0.0.1:3551"] ## Timeout for dialing server. timeout = "5s"
  6. There is an open issue on github for this https://github.com/influxdata/influxdata-docker/issues/118 The solution is probably to make a custom image that uses telegraf as the base image and then adds ipmi-tool. But sadly, I don't have time for that at the moment.
  7. What is the error message it is giving now?
  8. You need to remove the trailing slash from /mnt/cache/appdata/telegraf/telegraf.conf/
  9. you need to rename that to remove the .txt and change the mapping to be /mnt/user/appdata/telegraf/telegraf.conf
  10. You need to create that path and put the file telegraf.conf in the folder and then map to just the file. Find the file on the telegraf github.
  11. https://grafana.com/docs/installation/docker/ Just add an environment variable that corresponds to the setting you want to change. In that url they use -e "GF_SERVER_ROOT_URL=http://grafana.server.name" So in unRAID just edit the container, hit add variable and add the variable that changes what you want.
  12. In the first site they have telegraf running on pfsense (where NUT is installed) and they are running a shell script to gather up the data, and that telegraf instance sends the data to influxdb. You could do something like that.
  13. Use environment variables. See https://grafana.com/docs/installation/docker/
  14. There I just merged his latest into the mine. The docker container will auto build and be ready soon.
  15. I made the docker container because the original creator hadn't made one. so no, there isn't a docker container for his repo.
  16. I'd go to the github repo for this, he helps out and I think may have already fixed this issue. https://github.com/barrycarey/Speedtest-for-InfluxDB-and-Grafana I may need to pull his branch into mine so I can get the latest changes he has.
  17. The script should work for you now. If you have any more issues let me know.
  18. Thanks for the PR. I also just pushed a change to apcupsd-influx-exporter that doesn't hard code any outputs from apcupsd. This should handle all configurations now. It also adds a few more tags and cleans up the code in general.
  19. Not at the moment. I have a solution in the works, but no ETA.
  20. The problem is that the current program is hard coded to some outputs from apcupsd. Your ups doesn't have the battery voltage output, so it is breaking. Your welcome to submit a PR to fix that problem to the github project https://github.com/atribe/apcupsd-influxdb-exporter. Its something I want to do, just don't have the time right now.
  21. Don't know how to do that. I'd hit up the support link on the telegraf docker hub page or maybe their github page.
  22. Not sure, I didn't create that particular container, just made it available on unRAID. Find the it on dockerhub or github and ask the creator there.
  23. Based on the wiki for hddtemp https://wiki.archlinux.org/index.php/Hddtemp, it looks like you just put -q -d -F /dev/sd* /dev/nvme*
  24. Ok, fixed the problem. There was a missing package in the requirements file, so it wasn't working. The author also added a new section in the config.ini file. This is optional, however, it will log a an exception to the console if you don't have it. [LOGGING] # Valid Options: critical, error, warning, info, debug Level = info