So I added this monitor on to our file server to monitor a specific share and I know there is data on that share put the monitor returns a 0 value - have i set i tup wrong it says its up ..
Is there a directory on the S:\ drive of the server named "JBL_Users"? Also, if this is a network share that is mounted on the monitored server then this cannot be monitored remotely due to the multi-user nature of the Windows Operating System. E.G.using the server where the share is mounted essentially as a proxy to that remote storage. ORION_SERVER -> MONITORED_SERVER -> NAS_SERVER_SHARE. In cases such as this you would need to monitor the NAS server itself directly.
Its a Share on a file server on the s drive
r
So just to verify, this is not a mapped drive on the server. The storage is local to the monitored host?
Out of curiosity, how long have you had this component assigned to monitor this directory size and how many files are located under this share? It takes just as long (and sometimes a little longer) to determine the size of the directory as it does to calculate this value on the server itself by right clicking on the directory and selecting "properties". How long does it take to count up all the files, sub-folders, etc. using Windows Explorer?
Its not a mapped drive on the server its just a regular virtual server with drives off a san .. it has some data in the share and the share was brought on line this friday night
You're likely encountering an issue where the query to the server is timing out before before the result is returned. For almost 2TB of data comprised of nearly two million files it might not be possible to query this information reliably via WMI. You may need to use a script monitor and have it run only once an hour with a timeout value of an hour. WMI is designed for relatively quick queries. A recursive directory calculation of this size would easily take several minutes to complete. If it's longer than a minute or two then it's likely WMI on the remote host is terminating the request entirely waiting for the calculation assuming that it will never finish. You may however have success using the following template below. If not, I would suggest using remote PowerShell for such a large directory.
File and Folder Size Monitor Template
