Installing the Talend logging modules - 7.0

Talend ESB Installation Guide for Windows

Talend ESB
Installation and Upgrade
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Data Preparation
Talend Data Stewardship
Talend ESB
Talend Identity and Access Management
Talend Installer
Talend Log Server
Talend Runtime
Talend Studio
You need to manually install Talend Log Server which includes Kibana and Filebeat to collect logs.


  1. Copy and extract the archive file into the directory of your choice.
    Note: The directory name must not contain spaces or non-ASCII characters.
  2. To start Talend Log Server launch the start_logserver.bat executable file.
    You cannot run Elasticsearch as the root user. Elasticseach is part of the Talend Log Server, so you cannot run the executable file as root user.
  3. Configure the LOG_PATH and APP_NAME values for Filebeat in the filebeat.yml, located in the Filebeat directory.
    • Set LOG_PATH and APP_NAME to the following values:
          - ${LOG_PATH:C:\Talend\7.0.1\tac\apache-tomcat\logs\*}
          app_id: ${APP_NAME:TAC}
    • Or, set the LOG_PATH and APP_NAME environment variables:
      SET LOG_PATH=c:\Talend\7.0.1\tac\apache-tomcat\logs\*
  4. Start Filebeat:
    filebeat -e -c filebeat.yml


You can now access Talend Log Server with the following URL: http://localhost:5601/app/kibana#/dashboard/Default-Dashboard.

The ESB event logs that are displayed in the Logging page of Talend Administration Center are collected thanks to the Event Logging features that can be started from the Runtime container. For more information, see the Talend ESB Container Administration Guide.


When you start the Talend Log Server, if you do not see logstash-*, talendesb-*, and talendaudit-* indices, complete the following steps:

  1. Delete the .kibana index.
    curl -XDELETE 'http://localhost:9200/.kibana'
  2. Stop the Talend Log Server.
  3. Start the Talend Log Server.