Adding/Correcting page headers
This commit is contained in:
Родитель
4c04ef50dc
Коммит
78578fa224
|
@ -1,10 +1,17 @@
|
|||
# 00 - Setup your environment
|
||||
# Setup your environment
|
||||
|
||||
__This guide is part of the [Azure Spring Cloud Migration Lab](../README.md)__
|
||||
|
||||
Prerequisites and environment setup.
|
||||
|
||||
---
|
||||
|
||||
## Creating Azure Resources
|
||||
|
||||
To save time, we provide an ARM template for creating all the Azure resources you will need for this lab other than the Azure Spring Cloud instance itself. Use the Deploy to Azure button below.
|
||||
|
||||
> 💡 Use the following settings for deploying the Azure Template:
|
||||
|
||||
> * Create a new resource group
|
||||
> * Set West US2 as the location
|
||||
> * Save password you specify in this step, if you do not use the default. You will need it later in the workshop.
|
||||
|
|
|
@ -1,5 +1,11 @@
|
|||
# Migrate a Spring Cloud Application
|
||||
|
||||
__This guide is part of the [Azure Spring Cloud Migration Lab](../README.md)__
|
||||
|
||||
Provisioning an Azure Spring Cloud instance, configuring diagnostic settings and distributed tracing, building and deploying the application.
|
||||
|
||||
---
|
||||
|
||||
In this section, we're going to take a pre-existing Spring Cloud application, consisting of four microservices, and migrate it to Azure Spring Cloud in its entirety.
|
||||
|
||||
We will use this migrated application in the subsequent section to demonstrate the monitoring, scaling, and tracing capabilities of Azure Spring Cloud.
|
||||
|
|
|
@ -1,5 +1,11 @@
|
|||
# Troubleshooting
|
||||
|
||||
__This guide is part of the [Azure Spring Cloud Migration Lab](../README.md)__
|
||||
|
||||
Using Azure Log Analytics to understand what went wrong.
|
||||
|
||||
---
|
||||
|
||||
We have successfully migrated the application code to Azure Spring Cloud, but what happens when an application misbehaves?
|
||||
|
||||
## Query application logs
|
||||
|
|
|
@ -1,5 +1,11 @@
|
|||
# Observability and Scaling
|
||||
|
||||
__This guide is part of the [Azure Spring Cloud Migration Lab](../README.md)__
|
||||
|
||||
Using Distributed Tracing to understand microservice interactions, scaling out to meet demand.
|
||||
|
||||
---
|
||||
|
||||
After all the migrations, deployment, and automated deployment pipelines, all our microservices are up and running. But suddenly, something starts misbehaving. Intermittent errors start appearing when some action is taken, but where are they caused? Let's investigate.
|
||||
|
||||
## View distributed trace
|
||||
|
|
|
@ -1,5 +1,11 @@
|
|||
# Enable Continuous Deployment
|
||||
|
||||
__This guide is part of the [Azure Spring Cloud Migration Lab](../README.md)__
|
||||
|
||||
Creating automated build and release pipelines with Azure DevOps.
|
||||
|
||||
---
|
||||
|
||||
A key virtue of Microservices is the ability to continuously and independently test and deploy the changes to each one. In this section, we will set up pipelines to build and deploy one of the Microservices we migrated in Section 2.
|
||||
|
||||
## Create an Azure DevOps Project
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
# 04 - Enable Blue-Green Deployment
|
||||
# Enable Blue-Green Deployment
|
||||
|
||||
__This guide is part of the [Azure Spring Cloud Migration Lab](../README.md)__
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче