Simple Log Service:Create an alert rule for an OSS data shipping job of the new version

Step 1: Enable the service log feature for job operational logs

1. Log on to the Simple Log Service console.

2. In the Projects section, click the project that you want to manage.

   Click the project to which the OSS data shipping job belongs.

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

4. Go to the panel in which you can enable the service log feature for job operational logs.

   • If you did not enable the service log feature for detailed logs in the project, click Enable Detailed Logs on the Service Log tab.

   • If you enabled the service log feature for detailed logs in the project, click the icon on the Service Log tab.

5. Configure the parameters and click OK. The following table describes the parameters.

   Parameter	Description
   Job Operational Logs	If you turn on Job Operational Logs, Simple Log Service automatically creates a Logstore named internal-diagnostic_log in the project that you specify to store the operational logs and error logs of jobs such as Scheduled SQL jobs, MaxCompute data shipping jobs, OSS data shipping jobs, and data import jobs. For more information about log fields, see Operational logs of data transformation (new version) jobs, data import jobs and data shipping (new version) jobs.
   Log Storage Location	After you enable the service log feature for job operational logs, you must specify a project to store the logs. Valid values: Automatic Creation (Recommended) Current Project Other projects in the same region as the current project

   After you enable the service log feature for job operational logs, you can view the operational logs and error logs of OSS data shipping jobs in the internal-diagnostic_log Logstore of the specified project. The topic of the logs is etl_metrics. You can check the log topic in the __topic__ field. To query the operational logs and error logs of a specific data shipping job, you can execute a query statement in the job_name:Job name format. 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 page.

   1. In the Projects section, click the target project.

   2. In the left-side navigation pane, click Alerts.

   3. On the page that appears, choose Notification Management > Action Policy.

3. Find the action policy whose ID is sls.app.export.builtin and click Edit in the Actions column.

   You can also create an action policy to send alert notifications. For more information, see Create an action policy.

4. On the Primary Action Policy tab of the Edit Action Policy dialog box, change the value of the Request URL parameter to the webhook URL of your DingTalk chatbot. For other parameters, retain the default settings.

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

5. Click Confirm.

Step 3: Create an alert rule

Simple Log Service provides five built-in alert rule templates for data shipping. You need to only select a template based on your business requirements and create an alert rule from the template. In this example, an alert rule is created from the Data Export Delay Monitor template.

1. Log on to the Simple Log Service console.

2. In the Projects section, click the project that you want to manage.

   Click the project to which the internal-diagnostic_log Logstore belongs.

3. In the left-side navigation pane, click Alerts.

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

   

5. In the panel that appears, click Data Export Delay Monitor to create an alert rule. For more information, see Configure an alert rule.

   After the alert rule is created, view the alert rule in the list of alert rules. The alert rule is automatically enabled.

What to do next

After you create an alert rule for an OSS data shipping job, you can perform the following operations on the alert rule.