Use the Operation Content and Result Delivery feature

Configure delivery settings in the Elastic Compute Service (ECS) console

1. Log on to the ECS console.
2. In the left-side navigation pane, click ECS Cloud Assistant.
3. In the upper-left corner of the top navigation bar, select a region.
   Note O&M task execution records cannot be delivered across regions. To deliver O&M task execution records in multiple regions, configure delivery settings for each of these regions.
4. In the upper-right corner of the Cloud Assistant page, click Operation Content and Result Delivery.
5. In the Operation Content and Result Delivery dialog box, configure delivery settings.
   

   Note The first time you configure delivery settings, the system grants Cloud Assistant the permissions to access Log Service and OSS resources so that O&M task execution records can be delivered to your specified Logstore or OSS bucket. You can also manually manage the permissions. For more information, see Manage the service-linked role for Operation Content and Result Delivery.
   1. Select Deliver to Log Service. Then, select a created Log Service project from the Project drop-down list and a created Logstore from the Logstore drop-down list.
      If you have not created Log Service projects or Logstores in the selected region, click Log Service Console or Logstores to create projects or Logstores in the Log Service console. After you create projects or Logstores in the selected region, go back to the Operation Content and Result Delivery dialog box and click the icon to obtain the most recent list of projects or Logstores. For more information, see Manage a project and Manage a Logstore.

      Before you can query or analyze logs in Log Service, you must enable indexing. For more information, see Configure indexes.

      Notice The Operation Content and Result Delivery dialog box feature is free to use. However, you are charged for traffic generated when you use Log Service features such as indexing. For more information, see Overview.
   2. Select Deliver to OSS. Then, select a created OSS bucket and specify the root directory in which to store execution records.
      If you have not created OSS buckets in the selected region, click OSS console to create buckets in the OSS console. After you create buckets in the selected region, go back to the Operation Content and Result Delivery dialog box and click the icon to obtain the most recent list of buckets. For more information, see Create buckets.

      Notice The Operation Content and Result Delivery dialog box feature is free to use. However, you are charged for traffic generated when you use OSS features such as object management. For more information, see Billing overview.
   3. Click OK.

Query O&M task execution records in the Log Service console

This section describes how to access a specified Logstore from the ECS console to query logs about delivered O&M task execution records. Alternatively, you can log on to the Log Service console and access the specified Logstore.

1. Log on to the ECS console.
2. In the left-side navigation pane, click ECS Cloud Assistant.
3. In the top navigation bar, select a region.
4. In the upper-right corner of the Cloud Assistant page, click Operation Content and Result Delivery.
5. In the Operation Content and Result Delivery dialog box, click Logstores on the right of the Logstore field.
   For more information about how to query logs, see Query and analyze logs.

   The following figures show example logs about O&M task execution records. For information about parameters contained in the execution records, see the Parameters contained in O&M task execution records section in this topic.

   • Example log about one-time execution records (execution records of a command task that runs a command only once)
   • Example log about recurring execution records (execution records of a command task that runs a command on a recurring schedule)

     The Repeats value indicates the number of times that the command was run.

     
   • Example log about file-sending task execution records

Query O&M task execution records in the OSS console

This section describes how to access a specified OSS bucket from the ECS console to query objects that contain delivered O&M task execution records. Alternatively, you can log on to the OSS console and access the specified bucket.

1. Log on to the ECS console.
2. In the left-side navigation pane, click ECS Cloud Assistant.
3. In the top navigation bar, select a region.
4. In the upper-right corner of the Cloud Assistant page, click Operation Content and Result Delivery.
5. In the Operation Content and Result Delivery dialog box, click OSS Console on the right side of the Bucket field.
6. Go to the directory in which the object that contains the execution records of an O&M task is stored.
   After you log on to the OSS console, the system directs you to the root directory that you specified when you configured delivery settings in the Operation Content and Result Delivery dialog box. You can go to automatically generated subdirectories based on O&M task types.

   • For a command task, go to the invocationResults/<Execution ID> subdirectory. In this subdirectory, directories that are named after ECS instance IDs and the script of the command are displayed. The script may have one of the following names:
     • commandContent.bat: A batch command is run on specified Windows ECS instances.
     • commandContent.ps1: A PowerShell command is run on specified Windows ECS instances.
     • commandContent.sh: A shell command is run on specified Linux ECS instances.
   • For a file-sending task, go to the sendFileResults/<Execution ID> subdirectory. In this subdirectory, directories that are named after ECS instance IDs and the fileContent.txt file are displayed. The fileContent.txt file contains the sent content.

   The following figure shows an example subdirectory generated for a command task that runs a shell command on a Linux ECS instance.
7. Go to the directory that is named after the ID of an ECS instance to query the object that contains the execution records of tasks run on the instance.
   The following figures show example JSON-formatted objects that contain O&M task execution records.

   • Example object that contains one-time execution records
   • Example object that contains recurring execution records

     The digits in each object name indicate the number of times that the command was run on the specified instance.

     
   • Example object that contains file-sending task execution records
8. Click View Details in the Actions column corresponding to an object that contains execution records. Then, download the object or copy the object URL and view the object content.
   The following code shows an example object that contains the one-time execution records of a shell command. For information about parameters contained in the execution records, see the Parameters contained in O&M task execution records section in this topic.

   {
       "RegionId":"cn-hangzhou",
       "InstanceId":"i-bp1hd5ztmab9cgc0****",
       "InvokeId":"t-hz01x7rtjfy****",
       "CommandId":"c-hz01x7cn5aj****",
       "CommandName":"cmd-hostname",
       "CommandType":"RunShellScript",
       "CommandContent":"hostname",
       "ResourceOwnerUid":160998252992****,
       "CallerUid":160998252992****,
       "CallerType":"customer",
       "Timeout":60,
       "Frequency":"",
       "Parameters":"{}",
       "Username":"",
       "RepeatMode":"Once",
       "Repeats":1,
       "InvocationStatus":"Success",
       "Dropped":0,
       "Output":"iZbp1hd5ztmab9cgc0****\n",
       "ExitCode":0,
       "CreationTime":"2021-09-26T05:47:20Z",
       "StartTime":"2021-09-26T05:47:20Z",
       "UpdateTime":"2021-09-26T05:47:20Z",
       "FinishedTime":"2021-09-26T05:47:20Z",
       "StopTime":""
   }

Parameters contained in O&M task execution records