Skip to main content Skip to complementary content
Qlik Resources
Announcements
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Setting up the Logging parameters

About this task

In Talend Administration Center, there are two types of collected logs:

  • the technical logs, that gather technical events like the status of connections and servers, and so on.
  • the business logs, that gather all users' actions, like the creation, connection, deletion, and edition of a user, a Job and so on.

Those logs are collected by FileBeat and displayed on the Logging page thanks to the Kibana Web application whose URL needs to be configured in the Monitoring node of the Configuration page as explained in Setting up the link to the Monitoring modules. For more information about the extended logging module, see Displaying log events.

Information noteNote: Kibana is not supported on IE11.

You can modify the log file paths and threshold. To do so, complete the following:

Procedure

  1. On the Menu tree view, click Configuration.
  2. Click the Logs group to display its parameters.
    The parameters are editable according to your use:

    Parameter

    Value

    Technical file appender

    Type in the path to the technical log file of Talend Administration Center.

    The specified folder must exist. For example, if you enter c:/logs/technical.log, the technical.log file will be created in the existing c:/logs folder. The log file contains technical information logged by classes on the Talend Administration Center runtime, for example task execution start information and so on. You can safely remove the log file.

    Information noteNote: If no path has been set or if the path is invalid, the technical logs will be appended in Tomcat logs.

    Technical log threshold

    Select the level of logs you want to append between DEBUG, INFO, WARN, and ERROR from the drop-down list.
    Business log file path

    Type in the path to the business log file of Talend Administration Center.

    The specified folder must exist. For example, if you enter c:/logs/business.log, the business.log file will be created in the existing c:/logs folder. The log file contains business information logged by classes on the Talend Administration Center runtime, for example task or user create information and so on. You can safely remove the log file.

    Information noteNote: If no path has been set or if the path is invalid, the business logs will not be recorded.
    The format of the technical logs and the business logs follow the log4j Class PatternLayout. For more information see https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html. The conversion pattern %d{yyyy-MM-dd HH:mm:ss} %-5p %c{1} %x - %m%n is used:

    Conversion Character

    Effect

    %d{yyyy-MM-dd HH:mm:ss}

    Used to output the date of the logging event. The data format is yyyy-MM-dd HH:mm:ss, for example, 2018-02-07 18:58:15.

    %-5p

    Used to output the priority of the logging event. %-5p means the priority of the logging event should be left justified to a width of five characters, for example, INFO, WARN, DEBUG.
    %c{1}

    Used to output the Class name.

    %x

    Used to output the NDC (nested diagnostic context) associated with the thread that generated the logging event.

    %m

    Used to output the application supplied message associated with the logging event.

    %n

    Outputs the platform dependent line separator character or characters.
    A sample log 2018-03-14 09:36:17 DEBUG TokenRequiredPolicy - Checking token shows the following information:
    • datatime,
    • log level,
    • java class name,
    • the log message, which should include the activity detail.

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