Extension Filesystem monitoring can't make it work

[Jamie1]

Hi community,

I’m having trouble configuring the Dynatrace Filesystem Monitoring extension for one of the profiles. Below is the current configuration I’ve set up:

Check settings

• Check type: Modification age
• Path: (censor)
• File system: Local
• Run as: (account censor)
• Frequency: 60 minutes
• Use newest file: Enabled
• Days enabled: All days
• Schedule time: 06:00
• Schedule duration: 30 minutes

The extension is supposed to return the most recent file modification time (with "Use newest file" enabled). However, I’m not getting the expected results or behavior, and I’m unsure if the path, credentials, or other settings are causing the issue. 

Despite this configuration, I’ve encountered the following issues:

1. In the Data Explorer, under the metric file age, I’m getting a result of -1. From what I’ve read, this might be related to permission issues. However, as mentioned above, the (account censor) account should have the correct permissions to access the specified files.
2. I haven’t received any new data after three days of the configuration, even though the schedule and frequency appear to be configured correctly.
3. There’s a slider for Enable Debug, but I’m unclear on how to use it or where to locate the debug information after enabling it.

Could you help me understand why I might be seeing these issues and provide guidance on how to proceed, especially with using the debug feature?

[kalle_lahtinen · Accepted solution]

Yeah I think "-1" is a generic error which can mean anything related to not being able to fetch data; no permissions, directory does not exist, etc. Download the OneAgent support archive and navigate to the extension logs. I don't remember the exact path on OneAgent, but at least on ActiveGate it's \remotepluginmodule\log\extensions\datasources\<your_extension>

If you don't have access to the host where this extension is running, I would recommend installing OneAgent on a test host somewhere, and then test the config there first. At least I found it really hard to set this up remotely, when you don't see the actual directory structures and files. After the test setup works, you can more easily narrow down what's wrong in the real monitoring environment.