Installing the Talend logging modules

You need to manually install Talend LogServer which includes Kibana and Filebeat to collect logs.

Procedure

Copy and extract the Talend-LogServer-VA.B.C.zip archive file in the directory of your choice.

Information noteNote: The directory name must not contain spaces or non-ASCII characters.
To start Talend LogServer launch the start_logserver.bat executable file.
You cannot run Elasticsearch as the root user. Elasticsearch is part of the Talend LogServer, therefore you cannot run the executable file as root user.
Configure the values for LOG_PATH and APP_NAME for Filebeat:
- Open the filebeat.yml file located in the Filebeat directory and set the LOG_PATH and APP_NAME values as follows:
```
  paths:
    - ${LOG_PATH:C:\Talend\7.2.1\tac\apache-tomcat\logs\*}
  fields:
    app_id: ${APP_NAME:TAC}
```
- Or, set the LOG_PATH and APP_NAME environment variables:
```
SET LOG_PATH=c:\Talend\7.2.1\tac\apache-tomcat\logs\*
SET APP_NAME=TAC
```
Start Filebeat:
```
filebeat -e -c filebeat.yml
```

Results

You can now access Talend LogServer 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.

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

Delete the .kibana index.
```
curl -XDELETE 'http://localhost:9200/.kibana'
```
For Windows users, use the curl found in utils\curl-7.50.3-windows-x86.exe
Stop the Talend LogServer.
Start the Talend LogServer.

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