August 7, 20241 yr Varken starts fine for me and is running on 6.12.11, the dashboard has been updating as well.
August 7, 20241 yr On 7/12/2024 at 3:04 PM, T_Matz said: I was able to get most of the data added into the fields there are still a few sections that Im struggling with. All of this data is on unraid so I just dont know what i need to change in grafana I still cant get a few of these dashboards to work not sure where im missing the mark here
August 18, 20241 yr Hello. I am trying to get the panel to work, in the plex section of totals, I can't get the number to appear correctly. Thanks
August 21, 20241 yr Hey Everyone I was told to ask in this thread about what im looking to do. Id like to setup a cron that will iperf to a certain server (For speed tests) I have a multi-gig (10GE) connection that just doesnt work well with speedtest-cli and id like to graph it. Do any of you have anything like this setup? or is it part of this? Thank you!
August 24, 20241 yr Does anyone have a step by step video guide for the latest dashboard revision? Also the dependancies in the first post haven't been updated in a few years. Are they still relevant? Edited August 25, 20241 yr by urbanracer34
August 31, 20241 yr For those who have been using this for a while, (how) are you managing the size growth of your Telegraf Influx instance? Running since 2021, and now sitting at 106G du -sh * 152M _series 106G autogen /mnt/docker/appdata/influxdb/data/telegraf#
August 31, 20241 yr 45 minutes ago, wizzy said: For those who have been using this for a while, (how) are you managing the size growth of your Telegraf Influx instance? Running since 2021, and now sitting at 106G du -sh * 152M _series 106G autogen /mnt/docker/appdata/influxdb/data/telegraf# I have mine going to a zfs fileset with zstd-5 compression configured - heavy compression usually reaps significant benefits for time series data, and totally worth the (relatively small, at least in my experience, and with a modern processor) performance tradeoff.
November 25, 20241 yr Does anyone know why the time-series graph panels are all set to 6h? Its like they aren't respecting the time picker, nor the relative time options on the panel itself. This was for "Last 24 hours" in the time picker. Anything that does not modify query options is fine. If you make any modifications to query options, it snaps back to now-6h... EDIT: I found it. Under Dashboard Settings > General > Time Settings > Refresh Live Dashboards, Toggle that off. They all appear correct now. Edited November 25, 20241 yr by nate34k
December 5, 20241 yr On 8/24/2024 at 5:06 AM, urbanracer34 said: Does anyone have a step by step video guide for the latest dashboard revision? Also the dependancies in the first post haven't been updated in a few years. Are they still relevant? I have the same question as well ... Do you specifically have to use the versions of InfluxDB and Telegraf in the list of dependancies?
December 25, 20241 yr No you don't need to use the versions written in the dependency list. There have been many updates since that tutorial was written. Truth is most people on this thread set their system up long ago and the front-end GUI is really all that changes. The 2 or 3 backend parts just stay mostly the same. Nobody really documents the set up from scratch anymore. So here we are... I just installed this Dec 24th 2024 and here is what i did to get the basic install working. I still have to configure it to my environment, but its at least running. 1- Install InfluxDB 2 - I tried to use 1.8 as instructed, but other pieces later on seem to require version 2. I then went to localhost:8086 and set up the admin account. 2 - Installing Telegraf. For now, ignore all the unRAID instructions about enabling inputs. Getting Telegraf installed and running requires a config file. This file of course is not provided and the container wont start without it. Google provides you links to a now-deleted file. YOU WANT THIS >> https://raw.githubusercontent.com/influxdata/telegraf/master/etc/telegraf.conf It is located at the internet archive link because it does not seem to be anywhere else. GET THE FILE HERE >> https://web.archive.org/web/20230209014553/https://raw.githubusercontent.com/influxdata/telegraf/master/etc/telegraf.conf Copy the contents of that entire file. Its 10,000+ lines. Save it on you mac/PC somewhere, we will need it soon 3 - If you have already tried to start telegraf it has automatically created a folder for you in /mnt/user/appdata. You do not want them and it needs to be deleted. Open your unraid terminal and delete the /mnt/user/appdata/telegraf/telegraf.d folder I repeat - the telegraf.d folder. it is empty and we do not use it. If you are unsure how to delete the folder stop here. 4 - while you are in the /mnt/user/appdata/telegraf folder create the correct file with "touch telegraf.conf" Now you have a config file in the correct location. Type "nano telegraf.conf" Paste the 10,000 line file into nano with a right-click. Ctrl+O to save. Press Y then Enter. 5 - restart telegraf in the GUI and hope it stays running. This means your telegraf.conf file is being processed by the container. 6 - Install Grafana. You will need to tell it to use influx/telegraf as a data source. Follow the existing guide for that. 7 - Download the UUD dashboard template from this thread and follow the steps to make a dashboard. It will show nothing but errors, blanks and "N/A" Congrats. You did it. Now you can go back to the guide and follow steps for specific inputs you want to monitor. 8 - Follow the guide about inputs and outputs. This is where you make changes in the 10,000 line file. Rather than searching sections in the nano terminal, just use Ctrl+F in the local copy you saved on your local system. OUTPUT PLUGINS section starts at line 116 INPUT PLUGS section starts at line 3400 In nano you can jump to line numbers using Ctrl + <underscore>. Most people press "Ctrl" + "Shift" + "minus sign". The Shift and "dash-key/ minus sign" gives you the underscore needed. Type line number and press enter. 9 - Eventually you can add in things like Varken and Tautulli. 10 - Keep in mind every dashboard is unique to every system. So you will need to customize it. You can also try out older version of UUD as they don't have 30 HDDs configured and all sorts of stuff that have been added to the current version. You can have multiple dashboards at once so don't delete 1.7 if you want to try 1.3 I know I probably missed some stuff. I'll make updates as I find them. Edited December 26, 20241 yr by Somerandomaccount
December 31, 20241 yr I'm having an issue getting the time series working in grafana. I had this working about two weeks ago but I had to do a mobo swap on my unraid due to a hardware failure and it seems like the time series are messed up again. I have tried using different container versions but those have all not worked. At this point I'm sitting on the same versions that falcon states in the first post. I've checked the data itself and it seems like everything is there but for some reason the time series in grafana aren't being displayed correctly. Edited December 31, 20241 yr by Darigitin remove incorrect image
December 31, 20241 yr 20 hours ago, Darigitin said: I'm having an issue getting the time series working in grafana. I had this working about two weeks ago but I had to do a mobo swap on my unraid due to a hardware failure and it seems like the time series are messed up again. I have tried using different container versions but those have all not worked. At this point I'm sitting on the same versions that falcon states in the first post. I've checked the data itself and it seems like everything is there but for some reason the time series in grafana aren't being displayed correctly. I rolled grafana back to grafana/grafana:10.4.14 and this appears to have fixed it. I think there might be an issue when trying to run it on 11.
January 11, 20251 yr On 5/28/2024 at 8:22 PM, Jufy111 said: Where does this error occur? Is this in import error, or a panel error? So I'm actually getting this error too and I don't see that the original poster responded. I'm going through the initial setup of UUD and on the section with editing the telegraf.conf file and adding the post script to the docker container. "APK" does not work, but 'apt-get' does. if I open a console on the docker container while it is running, I can install the packages. when I add the line to the post arguments, I consistently get that error, even when doign something as simple as: "/bin/sh -c 'apt-get update'", it shows up under 'logs' after a failed start of the docker container.
January 11, 20251 yr 1 hour ago, octomobiki said: So I'm actually getting this error too and I don't see that the original poster responded. I'm going through the initial setup of UUD and on the section with editing the telegraf.conf file and adding the post script to the docker container. "APK" does not work, but 'apt-get' does. if I open a console on the docker container while it is running, I can install the packages. when I add the line to the post arguments, I consistently get that error, even when doing something as simple as: "/bin/sh -c 'apt-get update'", it shows up under 'logs' after a failed start of the docker container. Make sure that you a using the old version of telegraf. the newer versions will not let you install additional packages. telegraf:1.20.2 You can also just post this into the post argument. during the setup to save you longing into the console to install them /bin/bash -c 'apt-get update && apt-get install -y smartmontools && telegraf' Let me know if this fixes your issue
January 12, 20251 yr 14 hours ago, Jufy111 said: Make sure that you a using the old version of telegraf. the newer versions will not let you install additional packages. telegraf:1.20.2 You can also just post this into the post argument. during the setup to save you longing into the console to install them /bin/bash -c 'apt-get update && apt-get install -y smartmontools && telegraf' Let me know if this fixes your issue I lost my update trying to properly quote: the short answer is yes it worked, the not so short answer is, by pinning telegraf my other grafana dashboards do not work. I might have to simply not go this route so my other dashboard continues to work.
January 13, 20251 yr I am getting this issue from the telegraf docker with Unraid 7 (first time setup) 2025-01-13T03:27:05Z E! [inputs.docker] Error in plugin: Error response from daemon: {"message":"client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"} Anyone know how to resolve this? I assume I need to move to a newer version (currently testing with 1.20.2) but that seem to not work
January 18, 20251 yr On 1/13/2025 at 4:28 AM, blackert said: I am getting this issue from the telegraf docker with Unraid 7 (first time setup) 2025-01-13T03:27:05Z E! [inputs.docker] Error in plugin: Error response from daemon: {"message":"client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"} Anyone know how to resolve this? I assume I need to move to a newer version (currently testing with 1.20.2) but that seem to not work same for me after upgrade to unraid 7.0
February 3, 20251 yr First install today. Not a great start... I didn't modify anything in the config, is someone else having this problem? Having done nothing i don't really know how to solve it...
February 18, 20251 yr On 1/13/2025 at 4:28 AM, blackert said: I am getting this issue from the telegraf docker with Unraid 7 (first time setup) 2025-01-13T03:27:05Z E! [inputs.docker] Error in plugin: Error response from daemon: {"message":"client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"} Anyone know how to resolve this? I assume I need to move to a newer version (currently testing with 1.20.2) but that seem to not work Happened to me as well. I don't get docker metrics on my Ultimate Unraid Dashboard anymore.
February 18, 20251 yr So I don't use this dashboard, but I ran into this issue after upgrading from unraid 6.12.13 to 7.0.0. I did end up figuring this out. Set your Repository to: telegraf:alpine Then under Extra Arguments, add: --entrypoint=/bin/sh Lastly, this is the important bit. Under Post Arguments, ensure yours is like this: -c "apk add --no-cache sed && sed -i 's/su-exec telegraf/su-exec root/' /entrypoint.sh && apk update && apk upgrade && apk add smartmontools curl python3 py3-pip docker && python3 -m venv /venv && source /venv/bin/activate && pip install requests && exec /entrypoint.sh telegraf" To summarize what this is doing: Starts the docker container, and sets the entrypoint to be a shell session. Installs sed, to modify the entrypoint.sh within the docker container to update the su-exec from telegraf to root. Installs the other dependencies (adjust as you see fit). Sets up a venv for python, to ensure that package installs are able to be made (PEP 668 restrictions without this). Execute the original entrypoint.sh, but it's running as root now. As this is running as root, and not telegraf, be wary of the usual security issues. I'm not responsible for anything that happens Let me know if this works for you!
February 18, 20251 yr 43 minutes ago, ChrisTech said: Let me know if this works for you! Thanks for that, works for me. I had previously been using an old version as a workaround, but your method is a much better solution. Repository telegraf:1.20.2-alpine Post arguments /bin/sh -c 'apk update && apk upgrade && apk add ipmitool && apk add smartmontools && telegraf'
February 20, 20251 yr I don't know if this is a Grafana or a network problem, but every single dashboard on every port is showing "connection refused"? Edited February 20, 20251 yr by SteveScott
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.