Dynatrace Hub - Filesystem monitoring latest releases

Filesystem monitoring 2.1.0

Fri, 31 Jul 2026 18:26:15 +0000

Requires Dynatrace version 1.343.0 and EEC (OneAgent) version 1.310.0.

New in this version:

This extension is now using all rich visualization features of Grail within Infrastructure & Operations App.

Changed in this version:

Matches will no longer report WARNING or ERROR statuses if there is no match for a file check. This is consistent with the behavior of the extension before version 1.5.7.
If there are no matches for the defined check type, the metric value will report 0, with the exception of the filesystem.file_age metric, which will report -1 if no match is found.

Fixed in this version:

Individual metric values will now report for each check type, when multiple check types use the same path in a monitoring configuration.

Filesystem monitoring 2.0.3

Mon, 13 Jul 2026 19:38:00 +0000

Bugs Fixed in this version:

Resolved a bug in which the frequency set in the monitoring configuration was not respected when not utilizing the schedule feature.

Filesystem monitoring 2.0.2

Thu, 11 Jun 2026 12:57:19 +0000

WARNING: Possible breaking changes and warnings - PLEASE READ before upgrading:

This version requires a minimum Dynatrace version of 1.338.0 and a minimum EEC version of 1.310.0
This version includes a breaking change for Dynatrace on Grail.
- With the inclusion of OpenPipeline processing rules, any logs ingested from the extension will be processed by a dedicated OpenPipeline pipeline instead of the classic log pipeline.
- This means that classic rules will no longer be used on <metrics and/or logs> ingested from the extension. Please be sure to migrate any you still need to OpenPipeline rules.
- Additionally, some field names are handled differently in OpenPipeline, e.g. capitalization. Please double-check any custom dashboards and alerts you have created for this extension.
- You must opt-in to OpenPipeline configuration via Settings API – see the documentation.

New in this version:

Smartscape on Grail
Ability to mark no matches of a path pattern as a success criteria
- Configured via a toggle in the monitoring configuration for Count and Modification age count check types

Bugs Fixed in this version:

Resolved bug in which scheduled file checks did not start/end on time
Resolved behavior in which a check resulting in no matches was reported as an ERROR, now when a check results in no matches, it is returned as a warning if the check is not configured to have no matches as a success criteria

Filesystem monitoring 1.5.7

Thu, 26 Mar 2026 17:40:21 +0000

IMPORTANT: This version requires a minimum Dynatrace version of 1.318 and OneAgent version of 1.310

New Features

Advanced Scheduler
- Added support for more customized run schedules, allowing greater flexibility in configuration.
Dynamic Date Functionality
- Dynamic dates such as MMDDYYYY continue to function as before. However, you can now append paths like C:\DDMMYYYY|-1d, which will dynamically set the date to the day before the current run time. The extension performs the date calculation at each run.
Classic and Platform Dashboards bundled with extension

Security Improvements

Implemented additional validation of path parameter to prevent command injection.
Implemented additional validation of Azure account parameter to prevent SSRF.

Vulnerabilities Resolved

Resolved CVE-2026-21441 by updating urllib3 library to v. 2.6.3

Improvements

Implemented Endpoint Status reporting for each path in configuration for greater status granularity.
Enhanced logging by including Dynatrace Error Codes for improved debugging and issue tracking.
Defined screen for path entity in I&O app.

Bug Fixes

Resolved an intermittent issue where monitoring configurations with multiple assumed_user entries, each with different dimensions, could cause checks to fail.
Resolved an issue that affected execution due to daylight time change.

Filesystem monitoring 1.3.3

Tue, 19 Aug 2025 12:30:24 +0000

New Features

sesu has been added in the assume user options for linux hosts.

Filesystem monitoring 1.3.1

Tue, 01 Jul 2025 08:45:19 +0000

Bugfix

run_as Linux: dtuser correctly calls sudo when a username is omitted.

Filesystem monitoring 1.3.0

Tue, 17 Jun 2025 07:05:07 +0000

New Feature

Run As functionality implemented in Linux.
- This uses sudo when running checks. Which will call sudo as dtuser. But if the username field has a value it will run sudo -u <username>

Bug Fixes

Modification Age check has been fixed on glob patterns, now returns correct age.

Filesystem monitoring 1.2.2

Thu, 22 May 2025 13:50:36 +0000

Improves feel of monitoring configuration screen by moving check descriptions to Check type field tooltip

Filesystem monitoring 1.2.1

Tue, 06 May 2025 20:50:11 +0000

BugFix

Run_As functionality works as expected again

Filesystem monitoring 1.2.0

Wed, 16 Apr 2025 14:34:21 +0000

New Features

Added ability to enrich metrics with up to 3 additional metadata fields

Filesystem monitoring 1.1.5

Thu, 20 Mar 2025 11:53:29 +0000

New Feature

3 new dynamic dates where the month is a 3 character identifier
- DDMMMYYYY ex: 17MAR2025
- DDMmmYYYY ex: 17Mar2025
- DDmmmYYYY ex: 12mar2025

Bug Fixes

General

AzureFileCount works again.

Run_As bugfixes

Spaces in FileName will no longer break checks
Backslashes no longer disappear on the path dimension upon ingest to tenant
Logging Fix

Filesystem monitoring 1.0.1

Fri, 25 Oct 2024 18:52:26 +0000

New feature

Now has the ability to run as another user on windows hosts.
Running as user with permission to access network drives on windows hosts you are now able to query those network drives with selected check.

Filesystem monitoring 0.2.15

Tue, 07 Nov 2023 17:34:08 +0000

Fixed metric file age count when a file is modified during the check.

Filesystem monitoring 0.2.14

Thu, 24 Aug 2023 13:26:53 +0000

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).