Filesystem monitoringWith the filesystem extension V2, monitor your files on Windows and Linux OneAgent installations.
This extension offers more functionality than the previous version and uses the new extension framework (EF2.0).
The extension file no longer needs to be unzipped on your monitored hosts. The configuration and deployment is done via the Dynatrace User interface.
Targeting can be done by host, host group, management zone or environment. Tags can be applied to segregate your configurations (100 configurations maximum).
For each path check, Dynatrace will create an entity and link it to the matching host. This way, extension filtering and tagging is possible to view your data. The same can be done with alerts.
Checks can be disabled for specific days and at specific times.
File count: Number of files matching a pattern
File age count: Number of files matching a pattern and an age
File age: Age of a specific file (oldest or newest when returning more than 1 file)
File size: Size of the files in bytes
Mount point: Is a mount point mounted on Unix NFS
When schedule is not selected, the check will run 24/7.
If the check should not be performed on a Sunday, select schedule and untick Sunday.
Time windows can be added by entering the start time (use semi colon for multiple windows).
For each time, the schedule duration field will be added to determine the end. See example for only running from 10:00 and 12:00 for 1 hour.
The extension supports local file systems as long as the dtuser account can see the files.
The file must be at least readable by the Dynatrace user if not, it will be invisible to the extension.
On windows you are able to see NFS drives if you run_as another user and enter their information or choose the account from credential vault to run the checks as.
Azure file shares are supported too.
When selected, 2 new fields will appear. The azure account and the key.
Ensure that there is connectivity with azure from the oneAgent.
Go to the Dynatrace Hub and select the filesystem extension
Create a new configuration.
For each check press the add check button.
Select the check type and enter the relevant details.
Once done press next step.
Enter a description for your configuration and press Activate
Wait until the state of the deployment changes from pending to ok. This might take several minutes.
To view your data, go to the data explorer.
In the metric box type filesystem and select the relevant metric.
Metrics can be split by host, path
To drill down to the host or file check, hover on a data point and click on view path or view host list
If you are not getting the expected results, typically a metric with the value 0 (file size or count for instance) or -1 (file age), it is because the extension doesn't have sufficient privileges to see the folder content. The files are invisible to the extension and it will report the value 0 or -1.
Grant access to all users first in the location and try again. The value should be correct. Once done, narrow down the access to the correct account/group.
Do NOT use the file size metric for calculating the size of big volumes/mount points recursively such as c:\** as it will scan each file and time out.
The same applies to the other metrics when using recursive search with a very large number of files or sub directories.
For more information on which user runs the oneAgent:
Windows
Linux
This a OneAgent extension compatible with Windows and Linux.
Cluster version 1.254 and OneAgent 1.249 minimum.
Azure blob storage is supported
Fixed metric file age count when a file is modified during the check.
Added detection of modification time on folders.
Use /tmp/myfolder as path (with no wildcard) to return the most recently modified file date inside the folder.
Useful when files are very transient (appear less than 60 seconds) or with a very large number of files (no scanning required).
No release notes
Bug fix for mounts points with insufficient privileges errors.
No release notes
