You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/spring-apps/basic-standard/quickstart-setup-log-analytics.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,13 +25,13 @@ You can set up Azure Monitor Logs for your application in Azure Spring Apps to c
25
25
26
26
## Prerequisites
27
27
28
-
Complete the previous quickstart in this series: [Provision an Azure Spring Apps service](./quickstart-provision-service-instance.md).
28
+
Complete the previous quickstart in this series: [Provision an Azure Spring Apps service instance](./quickstart-provision-service-instance.md).
29
29
30
30
#### [Portal](#tab/Azure-Portal)
31
31
32
32
## Create a Log Analytics workspace
33
33
34
-
To create a workspace, follow the steps in [Create a Log Analytics workspace in the Azure portal](../../azure-monitor/logs/quick-create-workspace.md).
34
+
To create a workspace, follow the steps in [Create a Log Analytics workspace](../../azure-monitor/logs/quick-create-workspace.md).
35
35
36
36
## Set up Log Analytics for a new service
37
37
@@ -50,7 +50,7 @@ In the wizard for creating an Azure Spring Apps service instance, you can config
50
50
1. Fill out the form on the **Diagnostic setting** page:
51
51
52
52
-**Diagnostic setting name**: Set a unique name for the configuration.
53
-
-**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).
53
+
-**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).
54
54
-**Destination details**: Select **Send to Log Analytics workspace** and specify the Log Analytics workspace that you created previously.
55
55
56
56
:::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.
95
95
--query id --output tsv
96
96
```
97
97
98
-
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).
98
+
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).
*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.
21
+
*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.
22
22
23
-
While*App* runs the workload continuously, *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, and examples of jobs include batch processes and on-demand tasks.
23
+
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.
24
24
25
-
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 in Azure Spring Apps jobs efficiently to meet diverse requirements.
25
+
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.
26
26
27
-
## Execute a job
27
+
## Job execution
28
28
29
-
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.
29
+
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.
30
30
31
-
A common lifecycle of a job execution in Azure Spring Apps is from `pending`, `running`, to termination status `completed` or `failed` depending on whether the execution finishes successfully or not.
31
+
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.
32
32
33
33
Each time the job is executed, it adopts its preset configuration from the job, with certain aspects allowing for customization to accommodate different runs.
34
34
35
-
In nonparallel job execution, only one instance runs at a time. Whereas in parallel execution, multiple instances can run simultaneously.
35
+
In nonparallel job execution, only one instance runs at a time. In parallel execution, multiple instances can run simultaneously.
36
36
37
-
## Configure a job
37
+
## Configuration
38
38
39
-
The job establishes the default configuration utilized for each execution, encompassing elements like the user application source and trigger configuration. Each execution of the job inherits the configuration, allowing certain parameters to be overridden with new values for individual executions.
39
+
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.
40
40
41
41
The following table shows the configuration in job level or job execution level:
| Trigger type | Job | The manual trigger for public preview. More trigger types are supported later. |
46
-
| Parallelism | Job | The count of instances of the job that executes in the same time. The default value is 1. For parallel job, you can get the index of each instance through `JOB_COMPLETION_INDEX` environment variable. |
47
-
| Retry limit | Job | The maximum number of a job attempts to execution after encountering a failure or error. The default value is 0, which means the job doesn't retry if it fails. |
48
-
| Timeout | Job | The maximum time in seconds when the job failed. You can leave it unset or set the value at 0, which means the job has no timeout. |
49
-
| Arguments | Job/Execution | The value of arguments specified for the execution override of the job. |
50
-
| Environment variables | Job/Execution | The key-value pairs format. The environment variables specified in job level are default values for each execution. The environment variables specified in execution level have higher priority. You can specify part of those environment variables when start an execution to override the value in job level. |
51
-
| Secret environment variables | Job/Execution | The credentials, where the secret values are encrypted. |
52
-
| CPU | Job/Execution | The value of CPU specified for the execution override of the job. |
53
-
| Memory | Job/Execution | The value of Memory specified for the execution override of the job. |
54
-
55
-
The configuration on job level applies when creating or updating the job resource, and the configuration on job execution level applies when starting a job execution.
| Trigger type | Job | The manual trigger for public preview. More trigger types are planned for later. |
46
+
| 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. |
47
+
| 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. |
48
+
| 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. |
49
+
| Arguments | Job/Execution | The value of arguments specified for the execution override of the job. |
50
+
| 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. |
51
+
| Secret environment variables | Job/Execution | Variables that contain credentials where the secret values are encrypted. |
52
+
| CPU | Job/Execution | The value specified for the execution overrides the value specified for the job. |
53
+
| Memory | Job/Execution | The value specified for the execution overrides the value specified for the job. |
54
+
55
+
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.
56
+
57
+
## Next step
58
+
59
+
[How to manage and use jobs in the Azure Spring Apps Enterprise plan](how-to-manage-job.md)
0 commit comments