Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates

Changing the logLevel produced by LogServer

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
TalendSolutionExpert
Contributor II
Contributor II

Changing the logLevel produced by LogServer

Last Update:

Feb 9, 2024 1:22:49 PM

Updated By:

Jamie_Gregory

Created date:

Apr 1, 2021 6:05:30 AM

Problem Description

You want to produce smaller log files by configuring them to contain only error and warning messages, and not info messages.

 

Solution

Edit the logging level in the logging.yml file, located in the C:\Talend\x.x.x\logserv\elasticsearch-2.4.0\config folder, and change the log level from INFO to WARN or ERROR.

 

Your updated file should look similar to this:

#es.logger.level: INFO 
es.logger.level: WARN 
rootLogger: ${es.logger.level}, console, file 
logger: 
# log action execution errors for easier debugging 
action: DEBUG 

# deprecation logging, turn to DEBUG to see them 
deprecation: INFO, deprecation_log_file 

# reduce the logging for aws, too much is logged under the default INFO 
com.amazonaws: WARN 
# aws will try to do some sketchy JMX stuff, but its not needed. 
com.amazonaws.jmx.SdkMBeanRegistrySupport: ERROR 
com.amazonaws.metrics.AwsSdkMetrics: ERROR 

org.apache.http: WARN
Version history
Last update:
‎2024-02-09 01:22 PM
Updated by: