Alert Thresholds - Changing units Free Space datapoint on Volume Capacity
Hi All,
I wanted to put a question to you all to see if you have any recommendations. We have several drives that we are monitoring where it doesn’t make sense to track the % used datapoint due to the very large (or in a couple of cases, very small) total capacity of the drive. As such, we configured the Free Space datapoint for alerts instead. This is working well, however because the Free Space datapoint tracks “available storage capacity of the volume in bytes” it is difficult to quickly understand the potential impact of the alert when it triggers and error for < 268435456000 bytes remaining.
Is there any way to change this datapoint so that it reports in a larger unit? GB would be preferred, but even MB would be helpful.
HBanks_D3
Posted 3 years ago·Last reply 3 years ago
4 comments
LM User
·3 years agoYep. Just be careful: that module will be treated as custom by LM so it’s not supported and won’t get any updates. When/if the module toolbox gets to where it needs to be, if you just modified the existing one, you’d be able to bring in any updates and preserve the custom complex datapoint.
HBanks_D3
OP3 years agoThanks guys!
that was a simple one :) I must need another coffee.
John Mathews
·3 years agoHere’s a datasource that converts the bytes to gigs. Maybe you can use that as a template. MSFT reports it as bytes so that’s what WMI gets... Basically a complex dp that divides by 1024.
You can import this ds and apply tio to just one Windows server to see the ”effects”
LM User
·3 years agoCreate a custom datapoint that divides free_space by 1000 (KB), 1,000,000 (MB), or 1,000,000,000 (GB).
You could get fancy with it and have the divisor stored as a property so that you could have custom scaling on each one.