Obtain data from an ApsaraDB RDS for MySQL database over the internal network

Configurations

The following figures show how to configure data transformation rules and advanced parameters to obtain data from the ApsaraDB RDS for MySQL database over the internal network.

• Raw data
  • The following figure shows sample data records in a table of the ApsaraDB RDS for MySQL database.
  • The following figure shows a sample log entry in a Logstore of Log Service.
• Data transformation procedure
  1. Enable the data transformation feature in the source Logstore.
  2. Use the res_rds_mysql function to obtain data from the ApsaraDB RDS for MySQL database.
  3. Save the data transformation result to the destination Logstore.
• Transformation rule:

  e_table_map(res_rds_mysql(str_format("{}:{}",res_local("config.vpc.instance_id.test1"),res_local("config.vpc.instance_port.test1")), "your rds username", "your rds password", "your database",table="your table",primary_keys="bikeid"), "bikeid",["brand","batch"])

  Note You must use the following transformation syntax to access the ApsaraDB RDS for MySQL database over the internal network.
  Transformation syntax:

  e_table_map(res_rds_mysql(str_format("{}:{}",res_local("config.vpc.instance_id.name"),res_local("config.vpc.instance_port.name")), "database account", "database password", "database name",table="database table name"), "field", "output_fields")

  • You must set the same value for the name parameter in config.vpc.instance_id.name and config.vpc.instance_port.name, and the name parameter in the Advanced Parameter Settings section. You can customize the value.
  • The field parameter specifies the field that you want to map. This field exists in the Logstore and ApsaraDB RDS for MySQL database. If the value of the field in the Logstore is different from the value of the field in the ApsaraDB RDS for MySQL database, the data mapping fails.
  • The output_fields parameter specifies the output fields. If the data mapping succeeds, a new log entry is generated.
• Advanced parameter settings

  You must set Advanced Parameter Settings when you configure the preview mode and a transformation rule. For more information about how to configure other parameters, see Create a data transformation rule.

  

  You must set the same value for the name parameter in the config.vpc.vpc_id.name, config.vpc.instance_id.name, and config.vpc.instance_port.name parameters. The value must be the same as the name specified in the transformation rule. You can customize the value.

  Key format	Sample key	Sample value	Description
  config.vpc.vpc_id.name	config.vpc.vpc_id.test1	vpc-uf6mskb0b****n9yj	The vpc_id parameter specifies the ID of the VPC where the ApsaraDB RDS for MySQL database resides.
  config.vpc.instance_id.name	config.vpc.instance_id.test1	rm-uf6e61k****ahd7	The instance_id parameter specifies the ID of the ApsaraDB RDS for MySQL instance.
  config.vpc.instance_port.name	config.vpc.instance_port.test1	3306	The instance_port parameter specifies the internal endpoint of the ApsaraDB RDS for MySQL instance.

Troubleshooting

• A whitelist of IP addresses is not configured for the RDS instance.

  If the reason: {"errorCode": "InvalidConfig", "errorMessage": "error when calling : res_rds_mysql\nDetail: {\"errorCode\": \"InvalidConfig\", \"errorMessage\": \"Database connection failed, cause: (2003, \\\"Can't connect to MySQL server on '192.168.1.1' (timed out)\\\")\\nDetail: None\", \"requestId\": \"\"}", "requestId": ""} error occurs, Log Service is authorized to access the VPC where the RDS database resides. However, a whitelist of IP addresses is not configured for the RDS database. Therefore, Log Service cannot connect to the RDS database.

• Advanced parameters are invalid.
  • Different names are specified in the advanced parameters.

    If the reason: {"errorCode": "InvalidConfig", "errorMessage": "error when calling : res_rds_mysql\nDetail: {\"errorCode\": \"InvalidConfig\", \"errorMessage\": \"address check failed, please check the configuration of address. address: rm-bp***r5\\nDetail: None\", \"requestId\": \"\"}", "requestId": ""} error occurs, the name specified in config.vpc.instance_port.name parameter is inconsistent with the name specified in the config.vpc.instance_id.name, and config.vpc.vpc_id.name parameters.

  • Some advanced parameters are not specified.

    If the reason: {"errorCode": "InvalidConfig", "errorMessage": "error when calling : res_rds_mysql\nDetail: {\"errorCode\": \"InvalidConfig\", \"errorMessage\": \"address check failed, please check the configuration of address. address: rm-bp1***9r5\\nDetail: None\", \"requestId\": \"\"}", "requestId": ""} error occurs, the config.vpc.vpc_id.name parameter is not specified.

• The syntax of the transformation rule is invalid.

  If the reason: {"errorCode": "InvalidConfig", "errorMessage": "error when calling : res_rds_mysql\nDetail: {\"errorCode\": \"InvalidConfig\", \"errorMessage\": \"Database connection failed, cause: (2003, \\\"Can't connect to MySQL server on 'rm-bp***r5.mysql.rds.aliyuncs.com' (timed out)\\\")\\nDetail: None\", \"requestId\": \"\"}", "requestId": ""} error occurs, the syntax of the transformation rule is invalid.

Access an AnalyticDB for MySQL database or PolarDB for MySQL database over the internal network