EventBridge:Push events from ApsaraMQ for RabbitMQ to Function Compute

Step 1: Create a custom event source

1. Log on to the EventBridge console.

2. In the left-side navigation pane, click Event Buses.

3. In the top navigation bar, select a region.

4. On the Event Buses page, click the name of the custom event bus that you created.

5. In the left-side navigation pane, click Event Sources.

6. On the Event Source page, click Add Event Source.

7. In the Add Custom Event Source panel, configure the Name and Description parameters, select Message Queue for RabbitMQ from the Event Provider drop-down list, select the resources that you created for ApsaraMQ for RabbitMQ, and then click OK.

Step 2: Create an event rule

1. Log on to the EventBridge console. In the left-side navigation pane, click Event Buses.

2. In the top navigation bar, select a region. On the Event Buses page, click the name of the event bus that you want to manage.

3. In the left-side navigation pane, click Event Rules. On the page that appears, click Create Rule.

4. Perform the following operations in the Create Rule panel:

   1. In the Configure Basic Info step, enter a rule name in the Name field and a rule description in the Description field, and click Next Step.

   2. In the Configure Event Pattern step, set the Event Source Type parameter to Custom Event Source, select the custom event source that is created in Step 1 from the Event Source drop-down list, specify an event pattern in the Pattern Content code editor, and then click Next Step.

      For more information, see Event patterns.

   3. In the Configure Targets step, configure an event target and click Create.

      Note

      You can configure up to five event targets for an event rule.

      • Service Type: Select Function Compute.

      • Service: Select the service that you created in Function Compute.

      • Function: Select the function that you created in Function Compute.

      • Event: Select Template.

        The following part shows two sample variables and a sample template:

        Sample variables:

        {
          "source":"$.source",
          "type":"$.type"
        }

        Sample template:

        The event comes from ${source},event type is ${type}.

        For more information, see Event transformation.

      • Service Version and Alias: Select a service version or a service alias.

        • Default Version: The value is fixed to LATEST.

        • Specified Version: Select a service version. For more information, see Manage versions.

        • Specified Alias: Select a service alias. For more information, see Manage aliases.

      • Invocation Mode: Select Synchronous or Asynchronous. For more information, see Synchronous invocations and Overview.

Step 3: Publish an event

import com.rabbitmq.client.*;
import java.io.IOException;
import java.nio.charset.StandardCharsets;
import java.util.concurrent.TimeoutException;
import java.util.HashMap;
import java.util.UUID;

public class ProducerTest {
    public static void main(String[] args) throws IOException, TimeoutException {
        ConnectionFactory factory = new ConnectionFactory();
        // The endpoint. You can view the endpoint of the instance on the Instance Details page in the ApsaraMQ for RabbitMQ console. 
        factory.setHost("xxx.xxx.aliyuncs.com");
        // The username. You can view the username on the Static Accounts page in the ApsaraMQ for RabbitMQ console. 
        factory.setUsername("${UserName}");
        // The password. You can view the password on the Static Accounts page in the ApsaraMQ for RabbitMQ console. 
        factory.setPassword("${PassWord}");
        // Specify whether to enable automatic connection recovery. If you set this parameter to true, automatic connection recovery is enabled. If you set this parameter to false, automatic connection recovery is disabled. 
        factory.setAutomaticRecoveryEnabled(true);
        factory.setNetworkRecoveryInterval(5000);
        // The vhost name. Make sure that the vhost has been created in the ApsaraMQ for RabbitMQ console. 
        factory.setVirtualHost("${VhostName}");
        // The default port. Use port 5672 for non-encrypted connections and port 5671 for encrypted connections. 
        factory.setPort(5672);
        // The timeout period. Specify the value based on the network environment. 
        factory.setConnectionTimeout(30 * 1000);
        factory.setHandshakeTimeout(30 * 1000);
        factory.setShutdownTimeout(0);
        Connection connection = factory.newConnection();
        Channel channel = connection.createChannel();        
        channel.exchangeDeclare("${ExchangeName}", "${ExchangeType}", true, false, false, null);
        channel.queueDeclare("${QueueName}", true, false, false, new HashMap<String, Object>());
        channel.queueBind("${QueueName}", "${ExchangeName}", "${BindingKey}");
        // Send the message. 
        for (int i = 0; i < 100; i++  ) {
            // Set ${ExchangeName} to an existing exchange in the ApsaraMQ for RabbitMQ console. Make sure that the exchange type is consistent with that in the ApsaraMQ for RabbitMQ console. 
            // Set BindingKey to the corresponding binding key. 
            AMQP.BasicProperties props = new AMQP.BasicProperties.Builder().messageId(UUID.randomUUID().toString()).build();
            channel.basicPublish("${ExchangeName}", "${BindingKey}", true, props,
                    ("Message body"  + i).getBytes(StandardCharsets.UTF_8));
        }
        connection.close();
    }
}

Verify the results

To verify the results, you can view logs in the Function Compute console.

1. Log on to the Function Compute console.
2. In the left-side navigation pane, click Services & Functions.
3. In the top navigation bar, select a region.

4. On the Services page, find the service to which you routed the event and click Functions in the Actions column.

5. On the Functions page, click the name of the function to which you routed the event.

6. On the Function Details page, click the Logs tab to view logs.

   FC Invoke Start RequestId: c2be67a7-fh1a-9619-ei4c-3c04gcf6****
   2020-11-19T11:11:34.161Z c2be67a7-fh1a-9619-ei4c-3c04gcf6c**** [verbose] Receive Event v2 ==> The event comes from aliyun.ui,event type is ui:Created:PostObject.
   2020-11-19T11:11:34.167Z c2be67a7-fh1a-9619-ei4c-3c04gcf6c**** 
   FC Invoke End RequestId: c2be67a7-fh1a-9619-ei4c-3c04gcf6c****

FAQ

How can I locate the issue if the event fails to be published?

If an event fails to be published, you can view the response to the publishing request for troubleshooting. You can go to the EventBridge console and view the related information in the Event Delivery section of the Event Trace message. Then, take appropriate measures based on the response returned.

What can I do if an event fails to be published to Function Compute and the "[500]ConnectErrorconnectiontimedout" error is returned in the response?