Hi,
I have several DFS network shares I would like to monitor on free space left etc.
Does anyone know a plugin that could do it?
Any other info and advice is also appreciated.
Thank you.
Monitoring DFS share (free space etc.)
Re: Monitoring DFS share (free space etc.)
Here are the plugins I found:
https://exchange.nagios.org/index.php?o ... chword=dfs
Is it a domain integrated namespace or a standalone namespace?
The DFS namespace size will be limited to the size of the disk hosting the DFS namespace, you would likely want to just check the disk of the node hosting the DFS namespace.
https://exchange.nagios.org/index.php?o ... chword=dfs
Is it a domain integrated namespace or a standalone namespace?
The DFS namespace size will be limited to the size of the disk hosting the DFS namespace, you would likely want to just check the disk of the node hosting the DFS namespace.
-
bramassendorp
- Posts: 28
- Joined: Sun Jun 09, 2019 3:16 am
Re: Monitoring DFS share (free space etc.)
Hi,
All shares are on a NAS device, so it would be easier for us to just monitor the network share, of possible.
Thank you.
All shares are on a NAS device, so it would be easier for us to just monitor the network share, of possible.
Thank you.
Re: Monitoring DFS share (free space etc.)
Since we do not run DFS here you'll need to do the legwork and the testing of the plugins that exist.
You'll need to see if the caveat below impacts DFS shares (mounted per user, not per machine):
The recommendation being that you instead monitor the storage on the NAS instead of the mountpoint on the systems referencing it for free space usage.
You'll need to see if the caveat below impacts DFS shares (mounted per user, not per machine):
Taken from here (it's the best explanation I've seen, it has nothing to do with the agent, it's how windows and mapped drives works):Please note that UNC and network paths are only available in each session meaning a user mounted share will not be visible to NSClient++ (since services run in their own session). But as long as NSClient++ can access the share you can still check it as you specify the UNC path. In other words the following will NOT work: check_drivesize drive=m: But the following will: check_drivesize drive=\\myserver\\mydrive
Code: Select all
https://docs.nsclient.org/reference/windows/CheckDisk/