Editing an Event Subscription

If you set Event Target to FunctionGraph (function computing):

• Function: Select the function to trigger. If no function is available, create one by referring to Creating a Function.
• Version/Alias: Choose to specify a version or alias.
• Version: Select a version of the function. By default, latest is selected.
• Alias: Select an alias of the function.
• Execute: Select Asynchronously or Synchronously.
  NOTE:

  Function invocation mode. Default: Asynchronously.

  Asynchronously: Immediate responses of function invocation are not required.

  Synchronously: Immediate responses of function invocation are required.

• Agency: Select an agency. If no agency is available, click Create Agency to generate one named EG_TARGET_AGENCY.
  1. Only agencies with EG as the delegated cloud service are displayed.
  2. Select an agency with the permission functiongraph:function:invoke*.

If you set Event Target to Distributed Message Service (DMS) for Kafka:

• Connection: Select a DMS for Kafka connection.
• Topic: Select a message topic.
• Enable: Whether to enable the message key function.
• Transform Type: Defines how message keys are used. There are two options:
  • Variables: Keys are variable values from CloudEvents-compliant events.
  • Constants: Keys are specified constants. All messages will be sent to the same partition.

  For more information about the transform types, see Event Content Transformation.

If you set Event Target to EventGrid (EG):

NOTE:

An event can be transmitted three times in an EG channel.

• Account Type: Select Current or Other. The following table lists the parameters.

  Table 3 Event target parameters

  Current	Other	Description
  Region	Region	CN North-Beijing4, CN East-Shanghai1, CN East-Shanghai2, and CN South-Guangzhou NOTE: Coming soon in more regions.
  Project ID	Project ID	Enter the project ID of the target channel. NOTE: Enter the same project ID as the target channel, or events cannot be published to it. Obtain the project ID on the My Credentials page of the corresponding account.
  Channel	Channel	Enter the target channel ID. NOTE: Current account and same region: Select a channel in the current account. Other account: Specify a channel ID. If you select Current, select a different channel from the subscription. Do not select the default channel. When entering IDs across accounts, do not enter the same channel ID and default channel ID. Otherwise, the event cannot be delivered. If the current channel is not associated with a subscription, messages published to the channel cannot be consumed. Therefore, you need to add a subscription. The event source name of the downstream event subscription must be the same as that of the upstream event subscription, and the downstream event source must be a user-defined event source.
  Agency	Agency	Select an agency. NOTE: If no agency is available, click Create Agency to generate one named EG_TARGET_AGENCY. Only agencies with EG as the delegated cloud service are displayed. Select an agency with the permission eg:channels:putEvents.

  Rule:

• Transform Type: EG transforms CloudEvents-compliant events for targets.
  • Pass-through: Directly route CloudEvents-compliant events to the target.

  For more information about the transform types, see Event Content Transformation.

If you set Event Target to Simple Message Notification (SMN):

• Topic: Select a message topic.
• Agency: Select an agency. If no agency is available, click Create Agency to generate one named EG_SMN_PUBLISHER_AGENCY.
  • Only agencies with EG as the delegated cloud service are displayed.
  • Select an agency with the permission smn:topic:publish.
• Message Subject: Configure the subject through constants or variables.
• Type: Type of the message subject. Two types are available:
  • Constants: The subject does not change from specified. All messages will use the same subject.
  • Variables: The subject in the template is a variable value from CloudEvents-compliant events. Max.: 512 characters.
    NOTE:

    The Subject parameter is optional.

Rule:

• Pass-through: Directly route CloudEvents-compliant events to the target.
• Variables: Route variables in CloudEvents-compliant events to the target.
• Constants: Route constants in events to the target.

For more information about the transform types, see Event Content Transformation.

• Enter a request header.
• Enter a value.
• Specify whether to encrypt the header.
  Figure 4 Header parameters
  
  NOTE:

  • For custom HTTPS events, add authorization configurations for the event target to improve security.
  • If the request header and value are invalid, the encryption option is unavailable.
  • Key: Max. 256 characters starting and ending with a letter. Only letters and hyphen (-) are allowed.
  • Value: Max. 1024 characters, including letters, hyphens (-), underscores (_), spaces, and special characters (~!@#$%^&*()=+|[{}];:'",<.>/?).

• Pass-through: Directly route CloudEvents-compliant events to the target.
• Variables: Route variables in CloudEvents-compliant events to the target.
• Constants: Route constants in events to the target.

For more information about the transform types, see Event Content Transformation.