Merge pull request #276911 from Ratulac-Azure/ninpan/job

Edit "Add concept and how-to guide for job #274630"

Author: v-regandowner

articles/spring-apps/basic-standard/quickstart-setup-log-analytics.md

@@ -25,13 +25,13 @@ You can set up Azure Monitor Logs for your application in Azure Spring Apps to c
 
 ## Prerequisites
 
-Complete the previous quickstart in this series: [Provision an Azure Spring Apps service](./quickstart-provision-service-instance.md).
+Complete the previous quickstart in this series: [Provision an Azure Spring Apps service instance](./quickstart-provision-service-instance.md).
 
 #### [Portal](#tab/Azure-Portal)
 
 ## Create a Log Analytics workspace
 
-To create a workspace, follow the steps in [Create a Log Analytics workspace in the Azure portal](../../azure-monitor/logs/quick-create-workspace.md).
+To create a workspace, follow the steps in [Create a Log Analytics workspace](../../azure-monitor/logs/quick-create-workspace.md).
 
 ## Set up Log Analytics for a new service
 
@@ -50,7 +50,7 @@ In the wizard for creating an Azure Spring Apps service instance, you can config
 1. Fill out the form on the **Diagnostic setting** page:
 
    - **Diagnostic setting name**: Set a unique name for the configuration.
-   - **Logs** > **Categories**: Select **ApplicationConsole** and **SystemLogs**. For more information on log categories and contents, see [Create diagnostic settings to send Azure Monitor platform logs and metrics to different destinations](../../azure-monitor/essentials/diagnostic-settings.md).
+   - **Logs** > **Categories**: Select **ApplicationConsole** and **SystemLogs**. For more information on log categories and contents, see [Diagnostic settings in Azure Monitor](../../azure-monitor/essentials/diagnostic-settings.md).
    - **Destination details**: Select **Send to Log Analytics workspace** and specify the Log Analytics workspace that you created previously.
 
    :::image type="content" source="media/quickstart-setup-log-analytics/diagnostic-settings-edit-form.png" alt-text="Screenshot that shows an example of set-up diagnostic settings." lightbox="media/quickstart-setup-log-analytics/diagnostic-settings-edit-form.png":::
@@ -95,7 +95,7 @@ Setting up for a new service isn't applicable when you're using the Azure CLI.
        --query id --output tsv
     ```
 
-1. Configure the diagnostic settings. For more information on log categories and contents, see [Create diagnostic settings to send Azure Monitor platform logs and metrics to different destinations](../../azure-monitor/essentials/diagnostic-settings.md).
+1. Configure the diagnostic settings. For more information on log categories and contents, see [Diagnostic settings in Azure Monitor](../../azure-monitor/essentials/diagnostic-settings.md).
 
    ```azurecli
    az monitor diagnostic-settings create \

articles/spring-apps/enterprise/concept-job.md

@@ -0,0 +1,59 @@
+---
+title: Job in Azure Spring Apps
+description: Learn more about the Job concept in Azure Spring Apps.
+author: KarlErickson
+ms.author: ninpan
+ms.service: spring-apps
+ms.topic: conceptual
+ms.date: 06/06/2024
+ms.custom: devx-track-java, devx-track-extended-java
+---
+
+# Job in Azure Spring Apps (Preview)
+
+> [!NOTE]
+> Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
+
+**This article applies to:** ✔️ Java ✔️ C#
+
+**This article applies to:** ❌ Basic/Standard ✔️ Enterprise
+
+*Job* is a key concept in the resource model of Azure Spring Apps. Like *App* in Azure Spring Apps, both are considered resources managed within the service.
+
+An *App* runs a workload continuously, whereas a *Job* enables customers to run workloads that complete within a finite duration. Examples of apps include web apps and background services that process input continuously. Examples of jobs include batch processes and on-demand tasks.
+
+Spring developers who write jobs probably choose the Spring Batch framework or Spring Cloud Task. While Spring Batch excels in handling large-scale batch processing tasks, Spring Cloud Task is specialized for managing short-lived tasks with minimal overhead. You can run both types efficiently in Azure Spring Apps jobs to meet diverse requirements.
+
+## Job execution
+
+A *job execution* refers to the process of running a particular task or set of tasks defined within a job. It encompasses the entire lifecycle of executing those tasks, including initializing, processing, and completing the job according to its specifications.
+
+A common lifecycle of a job execution in Azure Spring Apps is from `pending` and `running` to a termination status of `completed` or `failed`, depending on whether the execution finishes successfully.
+
+Each time the job is executed, it adopts its preset configuration from the job, with certain aspects allowing for customization to accommodate different runs.
+
+In nonparallel job execution, only one instance runs at a time. In parallel execution, multiple instances can run simultaneously.
+
+## Configuration
+
+The job establishes the default configuration used for each execution, encompassing elements like the user application source and trigger configuration. Each execution of the job inherits the configuration, enabling certain parameters to be overridden with new values for individual executions.
+
+The following table shows the configuration in job level or job execution level:
+
+| Property name                | Scope         | Notes                                                                                                                                                                                                                                                                                                                       |
+|------------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Trigger type                 | Job           | The manual trigger for public preview. More trigger types are planned for later.                                                                                                                                                                                                                                            |
+| Parallelism                  | Job           | The count of instances of the job that executes in the same time. The default value is 1. For parallel jobs, you can get the index of each instance through the `JOB_COMPLETION_INDEX` environment variable.                                                                                                                |
+| Retry limit                  | Job           | The maximum number of times a job attempts execution after encountering a failure or error. The default value is 0, which means the job doesn't retry if it fails.                                                                                                                                                          |
+| Timeout                      | Job           | The maximum number of seconds to wait for a job to complete before its status is set to `failed`. You can leave it unset or set the value to 0, which means the job has no timeout.                                                                                                                                         |
+| Arguments                    | Job/Execution | The value of arguments specified for the execution override of the job.                                                                                                                                                                                                                                                     |
+| Environment variables        | Job/Execution | Variables in key-value pairs format. The environment variables specified at the job level are default values for each execution. The environment variables specified at the execution level have higher priority. You can specify environment variables when you start an execution to override the value at the job level. |
+| Secret environment variables | Job/Execution | Variables that contain credentials where the secret values are encrypted.                                                                                                                                                                                                                                                   |
+| CPU                          | Job/Execution | The value specified for the execution overrides the value specified for the job.                                                                                                                                                                                                                                            |
+| Memory                       | Job/Execution | The value specified for the execution overrides the value specified for the job.                                                                                                                                                                                                                                            |
+
+The configuration at the job level applies when creating or updating the job resource. The configuration at the job execution level applies when starting a job execution.
+
+## Next step
+
+[How to manage and use jobs in the Azure Spring Apps Enterprise plan](how-to-manage-job.md)

articles/spring-apps/enterprise/how-to-job-log-streaming.md

@@ -65,7 +65,11 @@ Use the following command to assign an Azure role:
 
 ---
 
-## List all instances in a job execution
+## View tail logs
+
+This section provides examples of using the Azure CLI to produce tail logs.
+
+### View tail logs for a specific instance
 
 Every time a job is triggered, a new job execution is created. Also, depending on the parallelism setting for your job, several replicas or instances execute in parallel.
 
@@ -79,11 +83,7 @@ az spring job execution instance list \
     --execution <job-execution-name>
 ```
 
-## View tail logs
-
-This section provides examples of using the Azure CLI to produce tail logs.
-
-### View tail logs for a specific instance
+You can get all instance names of the job execution from the output.
 
 To view the tail logs for a specific instance, use the `az spring job logs` command with the `-i/--instance` argument, as shown in the following example:
 
@@ -117,9 +117,15 @@ When you use the `-f/--follow` option to tail instant logs, the Azure Spring App
 
 ### Stream logs for a specific instance
 
-Use the following command to stream logs for a specific instance:
+Use the following commands to get instance names and stream logs for a specific instance:
 
 ```azurecli
+az spring job execution instance list \
+    --resource-group <resource-group-name> \
+    --service <Azure-Spring-Apps-instance-name> \
+    --job <job-name> \
+    --execution <job-execution-name>
+
 az spring job logs \
     --resource-group <resource-group-name> \
     --service <Azure-Spring-Apps-instance-name> \
@@ -158,7 +164,7 @@ Azure Spring Apps also enables you to access real-time job logs from a public ne
 
 Use the following steps to enable a log streaming endpoint on the public network:
 
-1. Select the Azure Spring Apps service instance deployed in your virtual network and then select **Networking** in the navigation menu.
+1. Select the Azure Spring Apps service instance deployed in your virtual network and then select **Networking** in the navigation pane.
 
 1. Select the **Vnet injection** tab.