Simple Log Service:Set up alerts for a MaxCompute data shipping job (new version)

Step 1: Enable job operational logs

1. Log on to the Simple Log Service console.

2. In the Projects section, click the target Project.

   This is the Project containing your MaxCompute data shipping job.

3. In the upper-left corner, click the icon.

4. Go to the page for enabling job operational logs.

   • If you have not yet enabled detailed logs for this Project, on the Service Log tab, click Enable Detailed Logs.

   • If you have enabled detailed logs for the Project, on the Service Log tab, click the icon.

5. Set the following parameters, and then click OK.

   Parameter	Description
   Job Operational Logs	When enabled, the system creates a Logstore named internal-diagnostic_log in the specified Project to store operational and error logs for scheduled SQL, MaxCompute shipping, OSS shipping, and data import tasks. For descriptions of the log fields, see Job operational logs for data transformation (new version), import, and shipping (new version).
   Log Storage Location	Specify a Project to store the logs. Select one of the following options: Automatic Creation (Recommended). Current Project. Other projects in the same region as the current Project.

   After you enable job operational logs, the operational and error logs of your MaxCompute data shipping job are stored in the internal-diagnostic_log Logstore of the specified Project. The log topic (__topic__) is etl_metrics. You can query the logs of a specific data shipping job by using a query statement in the format job_name:job_name, for example, job_name:job-1646****946.

Step 2: Configure an action policy

1. Log on to the Simple Log Service console.

2. Go to the Action Policy management page.

   1. In the Projects section, click any Project.

   2. In the left navigation bar, click Alerts.

   3. Select Notification Policy > Action Policy.

3. Find the target action policy (sls.app.export.builtin), and click Modify.

   You can also create a new action policy for alert notifications. For more information, see Action policies.

4. In the Edit Action Policy dialog box, on the First Action List tab, change the Request URL to the webhook URL of your DingTalk group chatbot. Keep the default settings for the other options.

   For more information about how to obtain the webhook URL for a DingTalk group chatbot, see DingTalk - Custom. You can also use other notification channels based on your business requirements. For more information, see Notification channels.

5. Click Confirm.

Step 3: Create an alert rule

Simple Log Service provides five built-in alert rule templates. Create an alert rule from a template based on your business needs. The following example uses the Data Export Delay Monitor template.

1. Log on to the Simple Log Service console.

2. In the Projects section, click the target Project.

   This is the Project where your internal-diagnostic_log Logstore is located.

3. In the left navigation bar, click Alerts.

4. On the Alert Rules tab, click Create from Template.

5. In the Create from Template pane, click SLS Data Shipping.

6. Click Data Export Delay Monitor.

7. Configure the parameters of the alert rule.

   • To monitor a specific project or adjust the trigger threshold, configure parameters as described in Create an alert rule. Otherwise, keep the default settings.

   • If you created a new action policy in Step 2, you need to configure it in Destination > SLS Notification > Action Policy.

8. After you complete the configuration, the Data Export Delay Monitor alert rule appears on the Alert Rules tab with a status of Enabled.

Related operations

After you set up alerts for your MaxCompute data shipping job, you can manage alert rules with the following operations.