falconexe
-
Posts
789 -
Joined
-
Days Won
15
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by falconexe
-
-
47 minutes ago, Marcjwebb said:
any video editors able to help?
got an m.2 coming today, for direct editing from the nas ( or for the fastest workflow), am i better leaving as an unassigned disk, then creating a share on that or using as SSD cache?
only thing is i don't want is the data moving itself across every evening as the project may need to be on the SSD for a week plus while i work on the project, then moving it across to the mechanical drives
I think it would better to have a share on the m.2 and then the main share with my mechanicals, then once I am done I can transfer from one to the other.
can anyone help shed some light as I haven't played with it this much for a while
I run a media production company on my UNRAID server. NVMe on Unassigned Drives share and a 10 Gig NIC card will give you awesome 1Gb/s SMB performance. Keep editing/projects separate from the array to avoid SFHS overhead while editing. Transfer projects/output manually or script movement to cache/array once you are done. Keep backups of your raw footage on parity protected array. Used copies of raw footage on the unassigned share for use while editing. Good luck!-
1
-
-
5 minutes ago, ptchernegovski said:
Ahhh, was going off memory, and for some reason thought you had said it was something for a future UUD.
Sorry for the confusion
No worries. It might me something I add if I end up getting a GPU. My chassis (45 Drives Storinator Q30 Turbo) is geared towards mass storage, and CPU/RAM performance, but not necessarily GPUs. I'd have to upgrade the PSU and drop some PCIe expansion stuff to do it. Maybe I'll use my old gaming rig to run a test bed UNRAID build with my old GTX 2080Ti (once I get my hands on a RTX 3080).
-
7 minutes ago, Dazog said:
I had my own dashboard for monitoring.
Just suggested it for people who don't want to make their own
If you are down, please post your Queries/JSON/screenshots of your NVIDIA GPU monitoring panels. It may help people like ptchernegovski.
-
1 hour ago, ptchernegovski said:
Looking good!
I have started playing with Varken a little for when 1.5 drops.
Really hope you can get an Nvidia panel or 2 working to show load, etc, for things like hardware transcoding in Plex. Or Folding at Home using those GPU's too....
I've covered this before.
On 9/17/2020 at 12:19 PM, Dazog said:Nvidia card monitoring for us peeps using nvidia custom unraid builds and future unraid builds with nvidia driver support baked in
On 9/23/2020 at 3:39 PM, falconexe said:Thanks for the feedback.
I am not running the beta yet, but I don't foresee any issues. I'll just have to keep adding support for new features. The problem is, I don't run my server with ALL features, so it would be hard to test. Some others have asked for NVIDIA GPU monitoring. This is all possible, but hard to develop for if I'm not rocking that architecture.
If you want to add NVIDIA GPU monitoring, check out the following:
https://github.com/influxdata/telegraf/tree/release-1.15/plugins/inputs/nvidia_smi
Once you install the plugin in Telegraf and enable it in the config, it should show up in the query window and you can start messing with it. IF, I ever end up putting a GPU into my UNRAID box, I'll bake it in. I just don't have any spare GPUs currently, and no more PCIe slots left that aren't filled with HBAs, 10Gig NICs, and PCIe NVMe adapters LOL.
-
Alright everyone. I have made some MAJOR updates/changes/additions to the Plex/Varken panels coming to the UUD version 1.5.
Starting with the upper panel, I turned this into a REAL TIME stream monitor that watches for activity every 30 seconds. I think it looks freakin sweet. The heat maps add a nice touch and give a 10,000 foot view of activity, and I really like the way the real time monitoring table came out with custom triggers, overrides, and formatting. Everything you would want to know about what and where exactly activity is coming from on your Plex server. I used 2 VPNs on this screenshot, and left my user account status mostly intact so you could see a full record. Other people, places and things are redacted where applicable. Let me know your thoughts.
New Dynamic Watched Percent (Really like the way this turned out!):
Current Stream Pie Charts:
Heat Map with Relative Dynamic Timeframes (Skew As Time Passes):
Full Top Panel (Plex Real Time Stats):
I'll preview/discuss the second row of panels in my next post!
-
40 minutes ago, Squid said:
There is a tradition that the new guy has to buy the beer....
I don’t drink beer but I do enjoy a good root beer. Henry Weinhard's is my go to. How many are there of us green shirts anyway? -
1 hour ago, snowmirage said:
I'm seeing the same behavior on 2 other computers. I started to try to look at the logs for grafana but haven't found them yet.
opening the console for the docker container I don't see a grafana.log file inside of /var/log/grafana in fact I don't see any files in there. Maybe they aren't visible to the grafana user?
/usr/share/grafana $ cd /var/log/grafana/
/var/log/grafana $ ls -lh
total 0
/var/log/grafana $/usr/share/grafana $ cd /var/log/grafana/ /var/log/grafana $ ls -lh total 0 /var/log/grafana $
I found a few topics that pointed me to a still active bug in grafana that maybe is related
https://github.com/grafana/grafana/issues/16638
but appears to be way back Version 6.1.4 we look to be on 7.2.1You can always right click on the Grafana docker and view the log there from the UNRAID GUI.
One difference is that I DO NOT use GUS, and manually installed all 3 dockers. I cannot attest to which version of Grafana is included in GUS, but you may want to confirm with Testdasi on that. Glad you found some breadcrumbs to follow at least. Let us know if you get it resolved.
-
Something really cool happened. I woke up this morning and my profile had this green wording on it.
I just officially became the newest UNRAID "Community Developer". I just wanted to say thanks to UNRAID and @SpencerJ for bestowing this honor. I am pleased to be able to add to the community overall. You guys rock! Honestly, I have been a part of many forums over the years, and I have never seen a community so eager to help, never condescending, always maintaining professional decorum, and overall just a great place to be.
I'm proud to be a part of it!
-
9
-
-
8 minutes ago, Forty Two said:
I'll get it working, and the whole setup looks great. I really appreciate the amount of work you've put into this.
Just a little bit disappointed that I have to start over.
I hear you. Unfortunately, there is no possible way to to carry forward anyone's modifications from a personal branch into a new release automatically. That being said, no one has to upgrade unless they want to, but my goal is to provide must have features in each release so that people will want to. This whole UUD concept takes work from both sides. It always has, and always will. It is just too dynamic of a situation. I look at the UUD as more of a foundation and insanely good template to start from.
I'm trying to make it as out of the box as possible, but due to the nature of this being based around user customization and infinite hardware combinations, it requires that special touch from each user to make it their own. My hope is that as people start messing with it, these concepts and skills will be built over time, and everyone who uses the UUD will gain knowledge. Then the end users can start sharing code and stuff they have built with the UUD community.
If you run on server hardware and can use IPMI, the UUD should just work out of the box with minimal effort like setting the upper variables. If you run on desktop/consumer hardware, you'll have to ditch IPMI, and use Sensors instead. That is where it takes some effort, but I have helped a few folks out there get up and running with Sensors, and it works great once you know how to bend it to your will.
I'm glad you think it looks great and I wanted to personally say thanks for your appreciation of my work. It means a lot!
-
7 hours ago, Forty Two said:
I just got 1.3 to work in full.
Very little works in 1.4, at least for me.
Just for example this is the code to get fan dials to work on my system:
SELECT last("fan_input") FROM "sensors" WHERE ("feature" =~ /fan./) AND $timeFilter GROUP BY time($__interval), "feature"Set ALIAS BY to:
$tag_featureOn each update (if you choose to use it) you will need to set the variables, datasources, and modify the queries again. If you want, you can just copy the JSON for a particular 1.3 panel you have modified (got working for your hardware) and just import it into the 1.4 dashboard. Alternatively, if there is something you must have from 1.4, you can do the opposite and import it into your working (stable) version of 1.3.
All kinds of options... FYI, many people have contacted me me and said that they love 1.4 and that it is working perfectly for them. So if 1.3 works for you, there should be know reason 1.4 won't work for you too. You'll just need to put some time into it. Let me know if I can help.
-
Hey everyone, I added a UUD News section to post # 1.
In case you didn't see, the UUD was featured in the official UNRAID monthly newsletter. I am super humbled to be included in that, and I wanted to thank the UUD community for making this what it is!
2020-09-28: The UUD is Featured in the Official UNRAID Monthly Newsletter (September 2020)!
-
And easy on your CPU ha ha it might burn up. Never seen an UNRAID server so pegged. Folding at Home is a beast.
Glad to know the RED CPU Core thresholds are working correctly LOL.
-
1 hour ago, ptchernegovski said:
Screenshot added to make people cringe at how full my drives are
And yeah, time for some more drives LOL!
-
1 hour ago, falconexe said:
Install TeamViewer and DM me your code and passcode. I’ll dial in and personally get this working for you. I’m just messing with computer stuff today anyway.
So for some reason, his sensors plugin would not work, even though it was installed correctly and we ran though the sensors-detect process. It didn't even work on UNRAID natively, so there may be something else going on with that server. If anyone else had run into this issue, and has a solution, let us know. Once you get the sensors issue resolved, your Telegraf should start reporting that module within Grafana and you can update your queries accordingly. @MrLondon has similar hardware and his sensors plugin worked perfectly.
-
2 hours ago, ptchernegovski said:
Have managed to follow @GilbN's guide from page 1, and have it mostly up and running, it looks great! Only things not showing are "system temps", and "system power". I am running a Ryzen 3600 on Nvidia Unraid 6.8.3 though.
Screenshot added to make people cringe at how full my drives are
Install TeamViewer and DM me your code and passcode. I’ll dial in and personally get this working for you. I’m just messing with computer stuff today anyway.
-
Well it’s most likely not Grafana because if it was a single internal setting, they should all log out around the same timeout. Very odd. I have my Grafana dashboards up 24/7 and the only time I ever have to log in again, is if I clear browser history (cookies). 🤷🏻♂️
Try another computer.
-
43 minutes ago, falconexe said:
Send me a quick TeamViewer invite (DM) and I can hop on real quick and see if we can figure it out. If we do, I'll screenshot the code and post it here.
For anyone using Sensors instead of IPMI for System Power, here is a query I just made on MrLondon's computer. It works great...
-
1
-
-
4 minutes ago, MrLondon said:
falconexe I just upgraded to 1.4 and changed the values to work on my system as I don't have user0 so had to change all to /mnt/user and then changed the cpu stuff to sensors like we did last week. Just with the system power is this possible with the sensors plugin? Fantastic release by the way. Keep up the amazing work.
Glad you like 1.4! Yeah if you don't run Cache, then you would use /mnt/user. That is why I updated all applicable panel descriptions to point that out. Glad that you saw that and that it made sense.
It should be possible to pull voltages from sensors on non server hardware. I would look around for a "feature" that looks like power readings. You'll have to play around with the query, just like we did on that virtual meeting we held. The 1.4 query uses IPMI and REGEX to pull anything with a unit of "Volts". That won't be possible with sensors, but there should be an equivalent catch-all, and/or you will have to add multiple queries to grab each voltage/component you want to monitor.
Send me a quick TeamViewer invite (DM) and I can hop on real quick and see if we can figure it out. If we do, I'll screenshot the code and post it here.
-
1
-
-
On another note, I just released the Ultimate UNRAID Dashboard Version 1.4!
@testdasi, feel free to include it with GUS in your next update.
Check it out Here:
-
2 hours ago, snowmirage said:
Cool thanks for the info, gives me a direction to troubleshoot in anyway! Thanks
No worries! Good Luck. Let us know what you find out. It may help someone else in the future.
-
-
43 minutes ago, falconexe said:
The Ultimate UNRAID Dashboard Version 1.4 is here! This is a MASSIVE 😁 update adding many new powerful features, panels, and hundreds of improvements. The main goal of this release is to increase usability and simplify the dashboard so more people can modify it without getting lost in REGEX and having to ask for support as often. As a result, the most complex queries have been rewritten in a way that is clear and transparent, while still remaining just as powerful. Finally, I have added requested features and threw in some new bells and whistles that I thought you guys would like. As always, I'm here if you need me. ENJOY!
@SpencerJ Feel Free to Update the Official UNRAID Press Releases. You can include my Reddit Handle now which is "TheRealJalexis".
-
43 minutes ago, falconexe said:
The Ultimate UNRAID Dashboard Version 1.4 is here! This is a MASSIVE 😁
Sorry for the wait. There was WAY MORE documentation than I thought. There were A LOT of changes ha ha.
I'm already working hard on Version 1.5 which will introduce a unified Plex/Varken Dashboard into the UUD. Stay tuned!
-
The Ultimate UNRAID Dashboard Version 1.4 is here! This is a MASSIVE 😁 update adding many new powerful features, panels, and hundreds of improvements. The main goal of this release is to increase usability and simplify the dashboard so more people can modify it without getting lost in REGEX and having to ask for support as often. As a result, the most complex queries have been rewritten in a way that is clear and transparent, while still remaining just as powerful. Finally, I have added requested features and threw in some new bells and whistles that I thought you guys would like. As always, I'm here if you need me. ENJOY!
Highlights:
-
Keep it Simple - Added User Transparency Back Into Dashboard by Removing REGEX on Certain Panels
- This Will Make it Extremely Easy to Customize the Dashboard to Your Specific Needs/Requirements
- You Can Now See Exactly How Certain Panels are Derived and Making Modifications is Self Explanatory
- This Will Also Make Support MUCH Easier For Everyone!
-
Multi-Host Support
- Change the Host Drop Down Variable and Monitor Another Host Instantly
- Added the Host Variable to Every Single Panel
- The Entire Dashboard Can Now Monitor Any Host in Real Time With a Single Variable Change Via Drop Down Menu!
-
Initial Support For Non Server Hardware
- Initial Support For Sensors Plugin to Monitor Non Server Hardware (Only Used If IPMI Is NOT Supported on Your Hardware)
- Requires New "sensors" Plugin (See Dependencies Section on Post #1)
-
Added Template Sensor Queries (Disabled By Default)
- You Will Need to Modify These Example Queries As Required For Your Non Server Hardware
- These are Just Building Blocks to Help Those Who Cannot Use IPMI
- Please See the Forum Topic For Detailed Help!
-
Initial Support For Unassigned Drives
- Added Ability For Unassigned Drives Via 2 Variables (Serial and Path)
- Added Unassigned Drives to Panels Throughout Dashboard Where Applicable
-
Default Dashboard Comes With Only 1 Unassigned Path Variable
- You Will Need to Add Additional Path Variables to Include/Exclude Multiple Unassigned Drive Paths
- Support For Multiple Cache Drives in DiskIO Graphs
- Support For Multiple Unassigned Drives in DiskIO Graphs
- Monitoring of ALL System Temps
- Monitoring of ALL System Voltages
- Monitoring of ALL System Fans
- Monitoring of RAM DIMM Temps
- Further GUI Refinements to Assist with Smaller Resolution Monitors
-
Variable Changes
-
Removed Redundant And/Or Unneeded Variables
- Cleans Up and Reduces Clutter Of Upper Variable Menu
-
Re-Ordered Variables
- Smaller Length Variables Are Now First (Typically Row 1)
- Longer Length Variables Are Now Last (Typically Row 2)
-
Standardized Dashboard to Use Single Datasource Instead of 3
- Before: Telegraf/Disk/UPS
- After: Telegraf
- This Also Keeps the Variables Menu Cleaner With Less Clutter (2 Less Variables!)
- Standardized All Variables Names in Title Case, Logical Prefixes, and Added Underscores to Separate Words
- Shortened Variable Label Text When/Where Possible
-
Removed Redundant And/Or Unneeded Variables
-
Changed All Panels to Use Default Min Interval Setting of Datasource
- Set Once in on Datasource and All Panels Not Explicitly Set Will Auto Adjust
- Only Those Panels Different From the Default Min Interval Are Now Explicitly Set (Example: Array Growth)
-
Modified and Added New Auto-Refresh Time Interval Options In Drop Down Menu
- Now: 30s,1m,5m,10m,15m,30m,1h,2h,6h,12h,1d
- Replaced All "Retro LCD" Bar Gauges With "Basic" (Cleaner GUI With Unified Aesthetic)
- Adjusted All Panel Thresholds to Be More Accurate on Color Changes (See Bug Fixes)
-
Added GROUP BY "time($_interval)" To All Panels
- Increases Overall Dashboard Performance
-
Removed Min/Max/Avg Values From All Line Graphs to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
- Corrected Various Grammatical Errors
- Bug Fixes and Optimizations
-
Hundreds of Other Quality of Life and Under the Hood Improvements
- You Can't See Them, But They're There...In Code...LOTS OF CODE
Bug Fixes:
- Changed Remaining Panels Using FROM "autogen" to "default"
-
Updated All Aliases to Match Panel Names
- There Were Still Some Discrepancies
-
Adjusted All Threshold Values to Be 1/10th Below Desired Measurement
- Forces Color Change on Next Whole Number
- Example: 90% Is Supposed to Be Red, But Would Still Show Preceding Orange Threshold Color (89.9% Resolves This)
New Panels:
-
Overwatch
-
System Temps
- Monitors ALL System Temps (Including CPU)
- Uses IPMI Unit "degrees_c" to Pull Values Instead of Individual Names
- Added/Modified Panel Description
-
-
System Power
- Monitors ALL System Voltages
- Uses IPMI Unit "volts" to Pull Values Instead of Individual Names
- Added/Modified Panel Description
-
-
Fan Speeds (Replaces Fan Speed Gauges):
- Monitors ALL System Fans
- Uses IPMI Unit "rpm" to Pull Values Instead of Induvial Names
- Also Fixes Issue Where Labels Were Not Being Dynamically Generated
- Added/Modified Panel Description
-
RAM Load:
- Show Current Ram Usage %
- Replaces RAM Used %
-
System Temps
-
Disk I/O
-
Unassigned I/O (Read & Write)
- Adds Support to Monitor Disk I/O of Unassigned Drives
-
Does Not Show Min/Max/Avg Values On Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
- Added Ability to Show Multiple Unassigned Drives by Serial Number
-
-
Unassigned I/O (Read & Write)
-
Disk Overview
-
Unassigned Storage
- Adds Support to Monitor Storage of Unassigned Drives
-
-
Unassigned Storage
-
Detailed Server Performance
-
RAM DIMM Temps
- Adds Support to Monitor RAM DIMM Temps
- Uses IPMI & REGEX
-
-
RAM DIMM Temps
Panel Changes:
-
Overwatch
-
ALL Subpanels
- Overhauled Look and Feel
-
Array Total
- Added Sparkline Graph
-
Array Utilized
- Added Sparkline Graph
-
Array Available
- Added Sparkline Graph
-
Array Utilized %
- Added Sparkline Graph
-
Cache Utilized
- Added Sparkline Graph
-
Cache Utilized %
- Added Sparkline Graph
-
CPU Load
- Added Sparkline Graph
-
RAM Load
- Added Sparkline Graph
-
1GbE Network
- Renamed Panel
- Changed to Orientation to Vertical
- Added Sparkline Graph
-
10GbE Network
- Renamed Panel
- Changed to Orientation to Vertical
- Added Sparkline Graph
-
Array Growth (Year)
-
Renamed Panel
- Previously Named "Array Growth (Annual)"
-
Renamed Panel
-
ALL Subpanels
-
DISK I/O
-
Cache I/O (Read & Write)
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
- Added Ability to Show Multiple Cache Drives by Serial Number
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
-
Array I/O (Read)
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
-
Array I/O (Write)
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
-
Cache I/O (Read & Write)
- Disk Overview
-
-
Array Disk Storage
- Added Used % Field
- Now Used to Indicate Drive Free Space By Color
- Modified Thresholds to Be More Accurate
-
Total Array Storage
-
Renamed Panel
- Previously Named "Array Storage"
- Added Used % Field
- Now Used to Indicate Drive Free Space By Color
- Modified Thresholds to Be More Accurate
-
Renamed Panel
-
Drive Temperatures
-
Renamed Panel
- Formerly "Drive Temperatures (Celsius)"
- Added Support For Unassigned Drives
-
Renamed Panel
-
Array Disk Storage
-
Detailed Server Performance
-
Network Interfaces (RX)
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
-
Network Interfaces (TX)
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
-
Network 1GBe
-
Renamed Panel
- Formerly "Network 1GBe (eth0)"
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Renamed Panel
-
Network 10GBe
-
Renamed Panel
- Formerly "Network 10GBe (eth2)"
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Renamed Panel
-
RAM
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
-
CPU Package
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
-
CPU 01 Load
-
Renamed Panel
- Formerly "CPU 01"
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed REGEX and Manually Set Cores Individually
- Increases Supportability
- Makes it Easier For Novice Users by Increasing Query Transparency
- Ensures Tags Stay Ordered Numerically (1,10,11...2,20,21... Is Now 1,2,...10...20...)
- Renamed Each Core With +1 Array Order Naming (Core 00 Now = Core 01...)
-
Renamed Panel
-
CPU 02 Load
-
Renamed Panel
- Formerly "CPU 02"
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Removed REGEX and Manually Set Cores Individually
- Increases Supportability
- Makes it Easier For Novice Users by Increasing Query Transparency
- Ensures Tags Stay Ordered Numerically (1,10,11...2,20,21... Is Now 1,2,...10...20...)
- Renamed Each Core With +1 Array Order Naming (Core 00 Now = Core 01...)
-
Renamed Panel
-
CPU 01 Core Load
- Changed Bar Gauge Type From "Retro LCD" to "Basic"
- Changed Bar Gauge Orientation to Vertical
-
CPU 02 Core Load
- Changed Bar Gauge Type From "Retro LCD" to "Basic"
- Changed Bar Gauge Orientation to Vertical
-
Fan Speeds
-
Renamed Panel
- Formerly "IPMI Fan Speeds"
-
Removed Min/Max/Avg Values From Line Graph to Decrease Screen Width Requirements
- Shows More Data on Smaller Screens
-
Renamed Panel
-
Network Interfaces (RX)
Updated Panel Descriptions:
-
Overwatch
-
System Temps
- Note: Uses IPMI
-
System Power
- Note: Uses IPMI
-
Fan Speeds
- Note: Uses IPMI
-
Array Total:
- Note: Change Path to "mnt/user" if Cache Drive is Not Present
-
Array Utilized
- Note: Change Path to "mnt/user" if Cache Drive is Not Present
-
Array Available
- Note: Change Path to "mnt/user" if Cache Drive is Not Present
-
Array Utilized %
- Note: Change Path to "mnt/user" if Cache Drive is Not Present
-
Array Growth (Day)
- Note: Change Path to "mnt/user" if Cache Drive is Not Present
-
Array Growth (Week)
- Note: Query Options > Min Interval - Must Match on Week/Month/Year To Stay In Sync Set to 2 Hours by Default For Performance Reasons) - Change Path to "mnt/user" if Cache Drive is Not Present\
-
System Temps
-
Disk Overview
-
Array Disk Storage
- Note: Uses Variable
-
Array Total Storage
- Note: Change Path to "mnt/user" if Cache Drive is Not Present
-
Unassigned Storage
- Note: Uses Variable
-
Drive S.M.A.R.T. Health Summary
- Removed Description
-
Drive Life
- Removed Description
-
Array Disk Storage
-
Detailed Server Performance
-
CPU 01 Core Load
- Removed Description
-
CPU 02 Core Load
- Removed Description
-
RAM DIMM Temps
- Note: Uses IPMI & REGEX
-
CPU 01 Core Load
Removed/Converted/Deprecated Panels:
-
Overwatch
- CPU 01 Temp
- CPU 02 Temp
- RAM Free %
- Fan Speed Gauges
Variables:
-
New
-
Drives_Unassigned
- Used to Select Unassigned Drives(s) From Drop Down Menu
-
Path_Unassigned
- Used to Set a Single Unassigned Drive Path For Inclusion/Exclusion in Drive Panels
- Add Additional Unassigned Path Variables to Include/Exclude Additional Unassigned Drive Paths
-
Drives_Unassigned
-
Renamed
-
Host
- Formerly "host"
-
Datasource_Telegraf
- Formerly "telegrafdatasource"
-
CPU_Threads
- Formerly "cputhreads"
-
UPS_Max_Watts
- Formerly "upsmaxwatt"
-
UPS_kWh_Price
- Formerly "upskwhprice"
-
Currency
- Formerly "currency"
-
Drives_Flash
- Formerly "flashdrive"
-
Drives_Cache
- Formerly "cachedrives"
-
Drives_Parity
- Formerly "paritydrives"
-
Drives_Array
- Formerly "arraydrives"
-
Host
-
Deprecated
- diskdatasource
- upsdatasource
See Post Number 1 For the New Version 1.4 JSON File!
-
3
-
Keep it Simple - Added User Transparency Back Into Dashboard by Removing REGEX on Certain Panels
whats the better option?
in General Support
Posted
Definitely. It’s what we do and it is the fastest architecture so far. Just don’t edit your raw footage without backups. Unassigned drive/share is not natively protected.