Configure third-party libraries

Procedure

1. Go to the Logstash Clusters page.

2. Navigate to the target cluster.

   1. In the top navigation bar, select the region where the cluster resides.

   2. On the Logstash Clusters page, find the cluster and click its ID.

3. In the left-side navigation pane, click Cluster Configuration.

4. In the Third-party Libraries section, click Manage next to Upload.

5. On the Modify Configuration page, click Configure at the bottom.

6. Click Upload and select local files to upload from the dialog box that opens.

   You can upload multiple files at once. Before uploading, Alibaba Cloud Logstash validates each file based on its name and MD5 value. Each file must have a .jar extension, and its filename cannot contain Chinese characters or exceed 100 characters. If a file fails this validation, an error message appears, and the file will not be uploaded.

   Currently, Alibaba Cloud Logstash supports three types of driver files: MySQL JDBC, PolarDB for Oracle JDBC, and PostgreSQL JDBC. The following table lists the download links.

   Driver type	Driver file
   MySQL JDBC driver	mysql-connector-java-5.1.27.jar mysql-connector-java-5.1.35.jar mysql-connector-java-5.1.39-bin.jar mysql-connector-java-5.1.39.jar mysql-connector-java-5.1.43.jar mysql-connector-java-5.1.47.jar mysql-connector-java-5.1.48.jar mysql-connector-java-5.1.9.jar mysql-connector-java-6.0.2.jar mysql-connector-java-6.0.6.jar mysql-connector-java-8.0.11.jar mysql-connector-java-8.0.17.jar mysql-connector-java-8.0.18.jar
   PolarDB for Oracle JDBC driver	PolarDB for Oracle JDBC.zip Note Alibaba Cloud PolarDB for Oracle provides JDBC drivers that are compatible with Java 6, Java 7, and Java 8. The corresponding JAR files are: polardb-jdbc16.jar polardb-jdbc17.jar polardb-jdbc18.jar Select the JDBC driver that matches your application's Java Development Kit (JDK) version.
   PostgreSQL JDBC driver	postgresql-42.0.0.jar postgresql-42.1.4.jar postgresql-42.2.0.jar postgresql-42.2.1.jar postgresql-42.2.8.jar postgresql-42.2.10.jar postgresql-42.2.13.jar

   Warning

   Modifying third-party libraries triggers a cluster restart. To avoid service interruptions, perform this change only during off-peak hours.

7. Click Save.

   Saving the configuration triggers a cluster restart. After the restart is complete, the third-party libraries are added.

8. Optional: Click Manage next to Upload again to view details of the uploaded files on the Modify Configuration page.

   The page displays the File Name and File Path for each uploaded file. You can copy a file's File Path to use when configuring a pipeline that requires that library. For a configuration example, see Use Logstash to synchronize data from RDS for MySQL to Elasticsearch.

   Important

   • For security, if you use a JDBC driver in your pipeline configuration, you must append allowLoadLocalInfile=false&autoDeserialize=false to the jdbc_connection_string parameter. Otherwise, the Logstash configuration file will fail validation. For example: jdbc_connection_string => "jdbc:mysql://xxx.drds.aliyuncs.com:3306/test-database?allowLoadLocalInfile=false&autoDeserialize=false".

   • To remove an unused third-party library, go to the Modify Configuration page, click Configure at the bottom, and then click the icon next to the file.

Related APIs

• ListExtendfiles: Queries the third-party libraries of a Logstash cluster.

• UpdateExtendfiles: Updates the third-party libraries of a Logstash cluster.