The monitor searches a Windows or Linux log file for text or regular expression and returns if a new line was found, and the last line number to contain the regex.

The Log File Scraper stores the last result and position in the monitored file in a Oracle, PostgreSQL, or SQL Server database so that it knows the last position the time it ran so it's not reading the same lines over and over. If the log file rolls over the monitor is smart enough to see that and starts from the beginning of the file again. The tables in the database (or App Mon Performance Warehouse) can be created by running the attached scripts. The scripts will create the table LogFileMonitor and LogRecords tables on the database.

Plugin Details

Plug-In Versions

Log File Monitor for Windows and Linux 3.16.6 (for dynaTrace >= 5.5)


  • com.logfile_3.16.6.jar: Plugin
  • MS_SQL_LogFileMonitor.sql: SQL Server Commands to create LogFileMonitor Table
  • MS_SQL_LogRecords.sql: SQL Server Commands to create LogRecords Table
  • Oracle_CreateTable.sql: Oracle Commands to create Tables
  • PostGreSQL_CreateTable.sql: PostgreSQL Commands to create Tables


Derek Abing

Joshua Raymond


dynaTrace BSD


Not Supported
If you have any questions or suggestions for these plugins, please add a comment to this page, use our forum, or drop us an email at apmcommunity@dynatrace.com!

Known Problems


Release History

2013-03-12 Initial Release for Windows Log Files Only

2013-12-18 Log File Monitor for Windows and Linux

2014-10-22 Update for Windows and Linux Monitor - 3.15.5

  • Added support for Oracle and PostgreSQL Databases
  • Improved plugin logging
  • Enhanced insertion of data into LogFileMonitor table

2015-04-09 Patch for Windows and Linux Monitor - 3.15.7

  • Improved logging for FileNotFound exceptions within Windows monitor
  • Improved hints within plugin configuration to indicate Windows monitor requirements

2016-06-19 Update for Windows and Linux Monitor - 3.16.2

  • Added support for SSH Keys
  • Added support for local Collector server logs

2017-03-17 Patches for windows compatibility

  • Defaulted Windows OS to "Local" connection method (even UNC file share paths are accessed "locally")
  • Fixed issue when using linux wildcards (Regexes)
  • Changed "ls" command parameter order to support Solaris OS

2018-01-11 Update for PostgreSQL Drivers and UTF-16 Encoding

  • Updated PostgreSQL Drivers
  • Included support for UTF-16 encoding in addition to the default UTF-8 support


Provided Measures

Line Number: The Line Number of the last known occurance of the specified search term.
New Message: Returns a 1 if a new entry was made to log file with the search term specified.
Number of Messages: The number of lines that matched the Search Term.




OSDropdown for selecting either Windows or Linux 
Connection TypeFor Linux connections, determines if a local log file or a remote host is being monitored (SSH) with relation to the AppMon Collector.
SSH TypeFor SSH connections, defines whether a password or public key is used for the SSH connection. Currently, only .pem keys are supported.
Linux UsernameLinux Username to use.
Linux PasswordLinux password to use


The network path to the shared filed on the server that contains the log file.
Example: /myapplication/logs/
This entry will be combined with the host name to create the network path to the file: //localhost/myapplication/logs/

File Regex

If this is selected then the file must be specified in terms of a regex expression.  If the directory contains multiple files that match the regex the newest file will be selected


The File that you wish to search.  If the File Regex option is checked, then this must be a regex. If running using Windows, this file must be shared to the user running the dynaTrace Collector.

Search Term

A regex of what you wish to search for within the log file.  The search is completed per line. Example .*Warning.*

Database TypeThe type of database where the log file scraper entries will be stored.

Database Server

SQL Server to contain the repository of log file searches

Database Port

Port to connect to on the database server. Default ports are:
Oracle: 1521, SQL Server: 1433, PostGreSQL: 5432

Database Name

The database to use for the log file repository.

Database Username

Username used to connect to the SQL Database

Database Password

The password for the username used to connect to the SQL database

Additional LinesAmount of additional lines to include in file after the log message is found 
Skip Additional Records If this box is checked, records included in the additional lines will be skipped for processing 
Keep Historical Record If this box is checked, a historical record of each log message will be added to the LogRecords database.  This database can then be queried for a list of all log messages matching a specific search and the corresponding timestamps 


Import the Plugin into the dynaTrace Server. For details how to do this please refer to the dynaTrace documentation.


Feel free to contribute any changes on Github