Note:The Workflows section of the MPS console has been replaced with Schemes, which offers easier and more flexible settings. To configure a scheme, go to Schemes.
After you set up a workflow, media files uploaded to the specified bucket and directory will be processed automatically, and the results will be uploaded to the specified bucket and directory. Workflows can include tasks such as transcoding, screenshot taking, animated screenshot generating, moderation, content recognition, content analysis, and watermarking.
The table below lists the information needed to configure a workflow.
Item | Required | Description |
---|---|---|
Workflow name | Yes | Max 128 characters; supports Chinese characters, letters, digits, underscores, and hyphens. Example: "MPS" |
Trigger bucket | Yes | Select a bucket created under the current `APPID`. After the workflow is enabled, videos uploaded to this bucket will be processed automatically. |
Trigger directory | No | A string that ends with (/) . If it is left empty, the workflow will be applied to all directories under the selected trigger bucket. |
Output bucket | Yes | By default, the output bucket is the same as the trigger bucket. You can also select a bucket in the same region under the same `APPID`. After a workflow is executed, the processed videos will be stored in this bucket. |
Output directory | No | A string that ends with (/) . If it is left empty, the output directory will be the same as the trigger directory. |
Event notifications | No |
|
Configuration items | Yes | From transcoding, screenshot taking, animated image generation, moderation, content recognition, and content analysis, select at least one task for configuration. For details, see task configuration below. |
Callback Method | Configuration |
---|---|
TDMQ-CMQ callbacks |
|
HTTP callbacks | When calling the notification configuration API TaskNotifyConfig, set `NotifyType` to `URL` and `NotifyUrl` to the HTTP callback address. |
SCF callbacks | You can click Go to SCF console to configure a function in the SCF console. For detailed directions, see MPS Task Callback Notification. SCF callback configuration applies to all workflows and is not saved specifically for the current workflow. |
SCF allows quick handling of the event notifications generated by MPS. The figure below shows the data flow.
Events are pushed to SCF by the MPS trigger and are handled by serverless functions.
CLS can deliver the data in log topics to SCF via an MPS log trigger to enable operations such as notification sending, status monitoring, and alarm handling.
Function Processing Scenario | Description |
---|---|
Video task backup to COS | Backing up the called back tasks of MPS to COS via SCF in a timely manner |
Video task callback notifications | Receiving MPS data messages in real time and sending the messages to users via WeCom or email. |
Note:Sending data to SCF will incur fees. For details, see Billing Overview.
Was this page helpful?