#JAVA FILEWATCHER WATCH FOR FILE TYPE INSTALL#
#JAVA FILEWATCHER WATCH FOR FILE TYPE DOWNLOAD#
#JAVA FILEWATCHER WATCH FOR FILE TYPE WINDOWS#

This will recursively generate file metrics for all files that match the glob pattern within TestFiles at all levels. Path: 'src/test/resources/TestFiles/**/*.*' This will recursively generate file and directory metrics for all files and subdirectories within TestFiles at all levels. This will generate file and directory metrics for all files and subdirectories within TestFiles only at the first level. This will generate file metrics for all log files within subdirectories of TestFiles that begin with '2020'. Path: 'src/test/resources/TestFiles/2020*/*.log' This will generate file metrics for files of all extensions within TestFiles. This will generate file metrics for only txt files withing TestFiles. Path: 'src/test/resources/TestFiles/*.txt' Refer to the Metrics section to differentiate between Directory metrics & File metrics. Path: 'src/test/resources/TestFiles/TF1.txt'įile metrics for TF1.txt will be generated in this case. Please ensure that the directory does not end with a slash for this scenario.

#JAVA FILEWATCHER WATCH FOR FILE TYPE WINDOWS#

(Note: For Windows, path should be configured with 4 backslashes as separator - C:\\src\\test\\resources\\TestFiles.įor Windows Network paths, you can configure path like - \\\\1.2.3.4\\abc\\def\\ProductI) 2.2.1 Monitoring a specific directoryĭirectory metrics for 'TestFiles' will be generated. There are multiple scenarios that can be configured in the pathsToProcess section. Consider our directory to be /src/test/resources/TestFiles. The actual path to the directories or files to be monitored. The following fields are present in each: 2.1 displayNameĪ mandatory field that acts as an alias for a configured path in the Metric Browser. The paths to be monitored must be configured under pathsToProcess. MetricPrefix: 'Custom Metrics|File Watcher| 2. If SIM is enabled, please use the default metric prefix. MetricPrefix: 'Server|Component:|Custom Metrics|File Watcher|' This can be done by adding the Tier ID to the metric prefix. Tier ConfigurationĬonfigure the Tier under which the metrics should be reported. If SIM is enabled, look for theĬonfigure the File Watcher Extension by editing the config.yml & monitor.xml files in /monitors/FileWatcher/. In the AppDynamics Metric Browser, look for: Application Infrastructure Performance||Custom Metrics|File Watcher.In the newly created directory 'FileWatcher', edit the config.yml to configure the parameters (See Configuration section below).Unzip the file FileWatcher-.zip into /monitors/.This will produce a FileWatcher-VERSION.zip in the target directory Run 'mvn clean install' from 'file-monitoring-extension'.Clone the 'file-monitoring-extension' repo using git clone command.For Windows network paths, it is recommended to map the paths locally prior to monitoring. The extension can be deployed on the same box as the one with the files to be monitored, or remotely if monitoring shared network paths.

#JAVA FILEWATCHER WATCH FOR FILE TYPE DOWNLOAD#

If your maven is using some other java version then please download java 8 for your platform and set JAVA_HOME parameter before starting maven. You can check the java version used in maven using command mvn -v or mvn -version.

#JAVA FILEWATCHER WATCH FOR FILE TYPE INSTALL#

Please do not proceed with the extension installation if the specified prerequisites are not met.ĭownload and install Apache Maven which is configured with Java 8 to build the extension artifact from source. Prerequisitesīefore the extension is installed, the prerequisites mentioned here need to be met.

The AppDynamics File Watcher Extension can be used to provide metrics from configured files and directories. AppDynamics File Watcher Extension Use Case

Java filewatcher watch for file type