Hi,
We have a workflow where users are copying files to a shared folder on Server A and these files are automatically copied to Server B using a service/process on Server A. So the users drop the files on Server A and eventually they will get copied from Server A to Server B.
Unfortunately, the service which copies the files from Server A to Server B isn't very reliable and sometimes crashes. Therefore I have setup a Folder sensor in PRTG which monitor the oldest files in the shared folder. If a file in the shared folder is older than 6 hours, then PRTG throws an alert. This tells use that the copy service has crashed and we need to restart it.
The problem I am facing in my specific scenario is that PRTG seems to monitor the "Date modified" field of a file and not the "Date created". When the files are copied to Server A from the users, the "Date created" is modified to reflect the time and date at which the copy was done. "Date modified" is unchanged as the file was not modified; it was only created on Server A during the copy. So sometimes, PRTG will throw an alert because a file just got copied from a user to Server A. The "Date created" field for that file is less than a few minutes, but the "Date modified" is more than 6 hours old because it hasn't been modified since.
Is it possible to configure PRTG to look at the "Date created" field instead of "Date modified" for that specific sensor/channel ?
We are running PRTG 19.4.54.1506 under Windows if this is relevant.
Thank you,
Guillaume.
Article Comments
Thank you Birk. I understand that the needs for this feature aren't high enough to justify the development of this in PRTG. I'll work on a script to fix this.
Thanks !
Feb, 2020 - Permalink
Hi there,
Thank you for your understanding. If you want to, you can also share your script here for other customers.
Have a great day.
Kind regards,
Birk Guttmann, Tech Support Team
Feb, 2020 - Permalink
Hi there,
I'm afraid, this option is not available and also not planned for the near future, since there are only few requests about this yet.
As workaround you can create a script or maybe apply a small change to the file while copying.
Kind regards,
Birk Guttmann, Tech Support Team
Feb, 2020 - Permalink