falconexe

1. Or you can set the unit to Data Metric Gigabytes and adjust the math. I did that on the flash (boot) panel. You can use that as an example.

No I just copied the JSON from the JSON overview. So if I export for sharing externally, it will default the variables? If so, good to know...

Glad to see you making progress!

@GilbN So I fixed that variable as you can see above, and when I export the JSON, I still see 2 references to "MassEffect" (My Host) hard coded. Is this OK and only because the value of that variable was actually set, and it is just exporting that value? And if so, can anyone else import my dashboard and simply change it? Or will this still cause issues? If it will cause issues, what should I override this too? Null values ""?

And fixed... I'll release in version 1.3.

IT WORKS! But I won't click on it because it lists all of the serial numbers LOL. Time for some hardcore override mapping. Guess I'll have to make a branched version for my personal dashboards, since putting overrides in using my serial numbers wouldn't be good for public distribution. 😜

Ahhhh. Yeah, I'll get that updated. I also found those 4 hard coded host names of "MassEffect". They somehow were in panels I turned into banners. So they were hidden. I just find and replaced them with $telegrafdatasource in the JSON and re-imported.

@GilbN So I've been trying to learn from your latest dashboard. I did some inverse Regex on the Array I/O panel to isolate the MD* instead of SD* (Like You Did) and it works pretty well. However, since Parity is not a part of MD because it is not in the array, I still have to use SD for those 2 drives. Which means they could still change on boot. Hence this new serial number route I am going to try across all panels if available. I'm not a huge Regex guy, and had to learn some syntax from you tonight, but the more I use it, holy cow it is powerful. You: Me:

You mean sleep 😂

Hey guys. I am hard at work in version 1.3 (bug fixes mostly). But I did come across something pretty interesting. There is a way to make drive order/mapping permanent by using the serial number of the drive. You have to add the following path to the Telegraf docker. Then Edit telegraf.conf > [[inputs.diskio]] > Add device_tags = ["ID_SERIAL"] > Use ID_SERIAL Flag is Grafana This means that upon booting, you don't have to worry about SD* changing, and you could override the serial number with "DISK01" etc. So the serials would never show unless you want them to. I will test and report back.

To be fair, there are use cases for both. I developed UUD to be as near to REAL TIME data as possible.

Upon starting dev on my version, I noticed that GilbN has many of his units set to non Metric which can very much skew results for us Westerners. So in the UUD, I completely remapped every single unit to match USA standards. Everything works and is accurate in my version. I have tested this extensively. Also in his version, many of those queries are using mean (average) where mine is using (last) which is the exact last measurement that Telagraf sent to InfluxDB. Not to mention padding... Example in his latest dashboard - mix of Metric (TB) and Non Metric units (Tib): I am working on fixing Version 1.2 now. I found those references to my server and will be updating them with the correct variable. I should have this ready tonight as version 1.21 as it is a minor bug fix.

No worries. Now that I know there are 4 instances of my Server in the JSON, I will go look at where those are coming from and make them dynamic. Thanks for looking into that. I'm working my normal job here to and trying to cook dinner as well. Let me know if you need some 1-on-1 help with getting your disk stats. It should be very simple. I'm down for a phone call if you want to DM me. I'm in the USA (Mountain Time).

@FreeMan Anyway, you making good progress? Things looking "pretty" yet?

Yes, you have 3 options that should work. NAS, default (which is NAS), or the datasource. All of these $variables should be "NAS" though because you set them in the top dashboard variables. If you happen to see "MassEffect" still in there anywhere on a query, let me know so I can investigate. Typically I try to match up the query topic with the correct dynamic variable. So if it is a disk query, I use the disk variable, UPS is. $ups etc. Everything else is just $telegraf. In mine, I just set it to use "MassEffect" because it was, in effect, the same thing since all 3 variables were set to that same string.

Ok thanks for letting me know.

@GilbNAnd how are you getting "=~" to show up, that is not an option for me? If I type it in, it reverts to "=".

I wonder if it is because I have this and others may not in the Telegraf docker config?

@GilbN So I watched the video and I still have the actual Query in there. Any idea why it would drop like that? Again, I made no changes here from your original template.

I'll run through them again.

@GilbN I just hard coded that variable in and it did not break, but when I reload the dashboard, it goes back to "MassEffect". 🤷‍♂️

So on the datasource variable, I just see "MassEffect" and "default" in the drop down. Should I default it to "$telegrafdatasource"?

No idea where that error is coming from then. Save your dashboard to a JSON file, and and then do a search for "MassEffect". We need to isolate where it thinks that is coming from. Also, you should be able to do a find and replace on that with "NAS" and it *MAY* fix it.

Above my pay-grade LOL. I wish I had the time to figure that out. I'm sure GilbN will figure it out (if he hasn't already).

Hey what do you have in this window? You'll need to add YOUR datasource here (remove mine). Let me know if that works and I'll update the instructions to include this bit.