Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-5875: How to Disable DA Logging

Auditing and Monitoring Service ,  

30 June,17 at 03:49 PM

This is correct setting the log to Warn will only collect events that are warning or higher. Info messages should not be collected. 

From Further looking into the audittrail.targets parameter you will need to set that to "1" if you want audit data sent to the collectors. 

There may be an issue as you reported that you are using 5.1.2 and this audittrail.targets functionality shows as being available starting in 5.1.3. 

Please test this on 1 5.1.2 system to see if this will work for you. 

Here is the explanation of audtitrail.targets parameter: 


This configuration parameter specifies the target for audit trail information. Possible 
settings are: 

0 - Audit information is not sent. 

1 - Audit information is sent to DirectAudit. This capability is supported by DirectAudit version 3.2 and later. 

2 - Audit information is sent to the local logging facility (syslog on UNIX systems, Windows event log on Windows systems). 

3 - Audit information is sent to both DirectAudit and the local logging facility. If DirectAudit 3.2 or later is installed, the default value is 3 (local logging facility and 
DirectAudit). Otherwise, the default value is 2 (local logging facility only). 

For example: audittrail.targets: 3