Use case for file availability check

How File Added check works

Working Principle:
When a file availability check is added and the specified file is created or deleted, the resource check status will move to Down   and an alert will be sent to the user. If the specified file is already present in the folder   while   adding the check ,   alerts will not be triggered. But if the file is added later, an alert will be triggered once the file is added. This is specific to file availability check for files added.

Example scenario :
A user creates a file called Log.txt in the D: drive . Then, the user sets up a File Added Resource Check profile in their Windows server. The check is set up in a way that an alert will be triggered if a file called   Log.txt is created. However , the user does not receive an alert.

Reason for not getting the alert :
The reason in this case is that the user had already created a file called Log.txt in the   D: drive and a File Added Resource Check was added in the Site24x7 client for that particular file when the same file already exists . So, even after the next data collection, the status remained as Up (green).


The user has to make sure that the resource check profile is created before the addition of the file. In this case :  

  1. Add a file availability check to send an alert once the file Log.txt is added.

  2. Make sure the option Alert when a resource check fails is set to Yes in the associated server's threshold profile to trigger a Trouble , Critical , or  Down alert for the configured check.

  3. To test if the alert is working, c reate a new file called Log.txt in the D: drive .

  4. When the file mentioned is added to the specified path, the status of the associated server monitor(s) will change to Trouble , Critical , or Down until the next data collection.