EventBridge:Push events from MNS 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 a custom event bus.
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, set the Name and Description parameters, select Message Service (MNS) from the Event Provider drop-down list, select a queue, and then click OK.

Step 2: Create an event rule

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 target event bus.
5. In the left-side navigation pane, click Event Rules.
6. On the Event Rules page, click Create Rule.
7. Complete the Create Rule wizard.
   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 Event 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. Then, click Create.
      Note You can configure a maximum of five event targets for an event rule.

      • Service Type: Click Function Compute.
      • Service: Select the service that you created in Function Compute.
      • Function: Select the function that you created in Function Compute.
      • Event: Click Template.

        The following part shows 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 Introduction to versions.
        • Specified Alias: Select a service alias. For more information, see Introduction to aliases.

Step 3: Publish an event

1. Log on to the MNS console.
2. In the left-side navigation pane, click Queues.
3. In the top navigation bar, select a region.
4. On the Queues page, find the queue to which you want to send a message. Choose More > Send Messages in the Action column.
5. In the Send Message section of the Quick Experience page, specify the Message Content and Scheduled Period parameters, and then click Send Message.
   "The message is sent" appears on the page.

Verify the result

To verify the result, 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 and Functions.
3. In the top navigation bar, select the region where your Kubernetes cluster is deployed.
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, find the function to which you routed the event and click the name of the function.
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

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?