Changing the Talend Remote Engine Job log level

It is possible to change the Talend Remote Engine log levels to align them with other Talend applications.

Tip: From Talend Remote Engine v2.8.3 onwards, set this log level in Talend Management Console when working with it, as this setting takes precedence over the configuration in Talend Remote Engine.

Procedure

Stop the Talend Remote Engine if it is running.
Open the <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.jobserver.client.cfg file.
Change the value of the job.log.level parameter.
- INFO
- WARN
- ERROR
- FATAL
As explained at the beginning of this section, from Talend Remote Engine v2.8.3 onwards, this setting is a fallback configuration, always overridden by the log level set in Talend Management Console when used.
By default, Fatal errors are displayed as Error logs. To make it explicitly displayed as Fatal logs in Talend Management Console, ensure that the job.log.fatal.level parameter is present in the <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.jobserver.client.cfg file and its value is true.
This makes the parameter read like:
```
job.log.fatal.level = true
```
This parameter applies to Talend Remote Engine v2.10.6 and onwards only.
Optional: If the log level is set to higher than INFO, ensure that the tJobLog components in your Job have the same or higher priority.
Optional: For Jobs published from Talend Studio V8.0 and onwards, if you need to ensure that the logs of a Subjob, that is to say, a child Job, is generated, add the following parameter:
```
job.log.subjobs.logs = true
```
For the previous Talend Studio versions, logs of a Subjob are not available if you select the Use an independent process to run subJob check box in tRunjob.
Save the file.
Restart your Talend Remote Engine.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here