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
> 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.
> 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.
> 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 shows you how to collect Spring Cloud Resilience4j Circuit Breaker Metrics with Application Insights Java in-process agent. With this feature, you can monitor the metrics of Resilience4j circuit breaker from Application Insights with Micrometer.
Copy file name to clipboardExpand all lines: articles/spring-apps/how-to-dynatrace-one-agent-monitor.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.devlang: azurecli
15
15
> [!NOTE]
16
16
> 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.
Copy file name to clipboardExpand all lines: articles/spring-apps/how-to-new-relic-monitor.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.devlang: azurecli
16
16
> [!NOTE]
17
17
> 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 explains how to set up a staging deployment by using the blue-green deployment pattern in Azure Spring Apps. Blue-green deployment is an Azure DevOps continuous delivery pattern that relies on keeping an existing (blue) version live while a new (green) one is deployed. This article shows you how to put that staging deployment into production without changing the production deployment.
22
22
@@ -76,13 +76,22 @@ To build the application, follow these steps:
76
76
1. Create the app in your Azure Spring Apps instance:
77
77
78
78
```azurecli
79
-
az spring app create -n demo -g <resourceGroup> -s <Azure Spring Apps instance> --runtime-version Java_17 --assign-endpoint
79
+
az spring app create \
80
+
--resource-group <resource-group-name> \
81
+
--service <Azure-Spring-Apps-instance-name> \
82
+
--name demo \
83
+
--runtime-version Java_17 \
84
+
--assign-endpoint
80
85
```
81
86
82
87
1. Deploy the app to Azure Spring Apps:
83
88
84
89
```azurecli
85
-
az spring app deploy -n demo -g <resourceGroup> -s <Azure Spring Apps instance> --artifact-path target\hellospring-0.0.1-SNAPSHOT.jar
@@ -114,7 +123,13 @@ To build the application, follow these steps:
114
123
1. Create the green deployment:
115
124
116
125
```azurecli
117
-
az spring app deployment create -n green --app demo -g <resourceGroup> -s <Azure Spring Apps instance> --runtime-version Java_17 --artifact-path target\hellospring-0.0.1-SNAPSHOT.jar
@@ -175,7 +190,12 @@ If you visit your public-facing app gateway at this point, you should see the ol
175
190
If you're not satisfied with your change, you can modify your application code, build a new .jar package, and upload it to your green deployment by using the Azure CLI:
176
191
177
192
```azurecli
178
-
az spring app deploy -g <resource-group-name> -s <service-instance-name> -n gateway -d green --jar-path gateway.jar
193
+
az spring app deploy \
194
+
--resource-group <resource-group-name> \
195
+
--service <service-instance-name> \
196
+
--name gateway \
197
+
--deployment green \
198
+
--jar-path gateway.jar
179
199
```
180
200
181
201
## Delete the staging deployment
@@ -185,7 +205,11 @@ To delete your staging deployment from the Azure portal, go to the page for your
185
205
Alternatively, delete your staging deployment from the Azure CLI by running the following command:
186
206
187
207
```azurecli
188
-
az spring app deployment delete -n <staging-deployment-name> -g <resource-group-name> -s <service-instance-name> --app gateway
> 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.
The `--main-entry` option specifies the relative path from the *.zip* file's root folder to the *.dll* file that contains the application's entry point. After the service uploads the *.zip* file, it extracts all the files and folders, and then tries to execute the entry point in the specified *.dll* file.
@@ -135,7 +139,11 @@ Use the following steps to deploy the SolarSystemWeather project.
135
139
1. Deploy the project to Azure.
136
140
137
141
```azurecli
138
-
az spring app deploy -n solar-system-weather --runtime-version NetCore_31 --main-entry Microsoft.Azure.SpringCloud.Sample.SolarSystemWeather.dll --artifact-path ./publish-deploy-solar.zip
@@ -293,7 +335,7 @@ The following steps show you how to generate configurations and deploy to Azure
293
335
294
336
1. Generate configurations by running the following command in the root folder of Pet Clinic containing the parent POM. If you've already signed-in with Azure CLI, the command automatically picks up the credentials. Otherwise, it signs you in with prompt instructions. For more information, see our [wiki page](https://github.com/microsoft/azure-maven-plugins/wiki/Authentication).
> 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.
@@ -30,30 +30,30 @@ The sample app is composed of two Spring apps:
30
30
31
31
* The `planet-weather-provider` service returns weather text in response to an HTTP request that specifies the planet name. For example, it may return "very warm" for planet Mercury. It gets the weather data from the Config server. The Config server gets the weather data from a YAML file in a Git repository, for example:
32
32
33
-
```yaml
34
-
MercuryWeather: very warm
35
-
VenusWeather: quite unpleasant
36
-
MarsWeather: very cool
37
-
SaturnWeather: a little bit sandy
38
-
```
33
+
```yaml
34
+
MercuryWeather: very warm
35
+
VenusWeather: quite unpleasant
36
+
MarsWeather: very cool
37
+
SaturnWeather: a little bit sandy
38
+
```
39
39
40
40
* The `solar-system-weather` service returns data for four planets in response to an HTTP request. It gets the data by making four HTTP requests to `planet-weather-provider`. It uses the Eureka server discovery service to call `planet-weather-provider`. It returns JSON, for example:
41
41
42
-
```json
43
-
[{
44
-
"Key": "Mercury",
45
-
"Value": "very warm"
46
-
}, {
47
-
"Key": "Venus",
48
-
"Value": "quite unpleasant"
49
-
}, {
50
-
"Key": "Mars",
51
-
"Value": "very cool"
52
-
}, {
53
-
"Key": "Saturn",
54
-
"Value": "a little bit sandy"
55
-
}]
56
-
```
42
+
```json
43
+
[{
44
+
"Key": "Mercury",
45
+
"Value": "very warm"
46
+
}, {
47
+
"Key": "Venus",
48
+
"Value": "quite unpleasant"
49
+
}, {
50
+
"Key": "Mars",
51
+
"Value": "very cool"
52
+
}, {
53
+
"Key": "Saturn",
54
+
"Value": "a little bit sandy"
55
+
}]
56
+
```
57
57
58
58
The following diagram illustrates the sample app architecture:
0 commit comments