Enable access to log content v1

Legacy Log Monitoring v1

You are viewing documentation for Log Monitoring v1. Dynatrace Log Monitoring v1, is considered a legacy solution.

Log Monitoring v1 will reach the end of life and will be switched off in November 2023.

SaaS environments will be automatically upgraded to LMA or LMC.

We strongly encourage you to switch to the latest Dynatrace Log Monitoring version.

If you are currently using Dynatrace SaaS, upgrade to the latest version of Dynatrace log monitoring.

To enable existing instances of OneAgent to access log content, log into the monitored host and set:

AppLogContentAccess = true

On Linux:

  • Dynatrace OneAgent versions 103 and later:
    /var/lib/dynatrace/oneagent/agent/config/ruxitagentloganalytics.conf

  • Dynatrace OneAgent versions 102 and earlier:
    /var/lib/ruxit/agent/config/ruxitagentloganalytics.conf

On Windows:

  • Dynatrace OneAgent versions 103 and later:
    %PROGRAMDATA%\dynatrace\oneagent\agent\config\ruxitagentloganalytics.conf

  • Dynatrace OneAgent versions 102 and earlier:
    %PROGRAMDATA%\ruxit\agent\config\ruxitagentloganalytics.conf

Dynatrace OneAgent restart is not required.

New installations

By default, Log Monitoring is enabled by your Dynatrace administrator during Dynatrace OneAgent installation. If you don't want to allow access to log files on a particular host, you can disable Log Monitoring for that host during Dynatrace OneAgent installation. In the Linux installation example below, note the Enable access to monitored processes log files content on this host switch. Disable this setting to turn off log access for this host. The Dynatrace OneAgent installer for Windows provides the same option.

Analytics 1

For both operating systems, Dynatrace OneAgent installation provides support for the --set-app-log-content-access parameter, which sets log access to either enabled or disabled based on the state of this switch.