Add log files manually

Dynatrace allows you to add specific log files manually in instances where the files aren't discovered automatically. You only need to add one log path at the process-group level to cover all processes within the group across all monitored hosts.

Adding log file to process group

To manually add a log file to a process group

1. In the Dynatrace menu, select Technologies and processes and a process group.
2. From the process group page, select the process instance for which you want to add a new log file.
3. In the Log files section of the page, select the Configure more log files link.
   Alternatively, look for the No log sources detected section if no log files are associated with the process.
4. On the Process group settings page, select the Log monitoring tab.
5. Select Add new log for monitoring.
6. Type the file path of the log file to be associated with this process group. Only absolute paths are allowed.
7. Select Save.

Windows event logs

You can add a custom event log to a process.

To manually add a custom Windows event log file to a process

1. In the Dynatrace menu, select Hosts.

2. Select the host that contains the Windows event log file.

3. From the Processes section of the overview of the host page, select the process for which you want to add a new log file.
   Optionally, in the Dynatrace menu, go to Technologies and processes, select a process group, and then, from the process group page, select the process instance for which you want to add a new log file.

4. In the Log files section of the page, select the Add more link.

5. On the Manually added process logs page, select Add new log for monitoring

6. Provide the log name followed by the .evtx file extension.
   You can use the built-in Windows Event Viewer to find the custom log name. Make sure that you provide the full path.

   Example

   As in the following example, you can display the log name by right-clicking on the chosen event log and selecting Properties:

   

   Copy the Full Name:

   

7. Select Save.

Considerations for adding text log files manually

Dynatrace supports log files that were updated (written to) in the last 7 days AND meet at least one of the following criteria:

• Files are located in a directory called log or logs (limited up to 2 levels) or /var/log/.
  OK:
  C:\Program Files\MyApp\logs\aaa.txt
/var/log/app/other/out/bbb.out

  NOT OK:
  C:\Program Files\MyApp\logs\other\out\ccc.txt

• Custom log path must specify files, not a directory:
  NOT OK:
  /var/log/customdir/

• Custom log paths files must not start or end with a wildcard ( * )
  NOT OK:
  /var/log/customdir/*
/var/log/customdir/file*
/var/log/customdir/*.log

• Files have the extension .log (for example, apache.log).

• File names (excluding optional additional extension) end with [.-_]log (for example, apache_log.txt, apache.log.txt, or apache-log.txt).

Additionally:

• Only absolute file paths are supported:
  • Unix: Path must begin with /.
    Paths within the following folders are not supported:

  copydownload
  etc
  boot
  proc
  dev
  bin
  sbin
  lib
  usr
  .ssh

  • Windows: Path must begin with drive letter (for example, C:\ ).
    Paths within the following folders are not supported:

  copydownload
  windows
  winnt

• Manually added log files affect all processes on all hosts belonging to the configured process group.
• To add log files located in a container:

1. Configure the container so that the log file within the container is written to a disk.
2. Point the OneAgent to this location by defining the absolute path to where the container is to write the log files.

• You can add numbered rotating-log filesets by using the hash character (#).
  For example, /var/log/error-#.log will match error-1.log, error-2.log, etc., and report the fileset as a single error-#.log file.

• You can globally disable the option to configure custom log files by setting:
  AppLogRemoteConfiguration = false

  On Linux:
  /var/lib/dynatrace/oneagent/agent/config/ruxitagentloganalytics.conf

On Windows:
%PROGRAMDATA%\dynatrace\oneagent\agent\config\ruxitagentloganalytics.conf