What’s New in Azure Spring Cloud – January Update

This post has been republished via RSS; it originally appeared at: Microsoft Developer Blogs - Feed.

Microsoft and Pivotal co-announced Azure Spring Cloud private preview on SpringOne Platform keynote and then public preview on Microsoft Ignite in last quarter. It is a fully managed service jointly built, operated, and supported by Pivotal and Microsoft, to simplify spring boot based microservices development and management. We would like to thank all our preview customers and the feedback you’ve given so far. As we have been committed to making Microsoft Azure an excellent cloud for Java workloads, we continue to deliver more per customers’ requests and feedback. In this blog, I’ll share the newest features on diagnostics and guidance on CI/CD from the January release of Azure Spring Cloud.

Log Streaming

In Azure Spring Cloud, Spring developers can enable Log Analytics to view or query logs with a few minutes latency to ingest log data. Log streaming feature allows developers to get real-time application logs in Azure CLI and know what’s happening with specified application instance running in Azure Spring Cloud. Below is an example and you could get more details here.
$ az spring-cloud app log tail -g AzureSpringCloudDemo -s demo -n gateway
If you have multiple app instances, you will get the names of those app instances after running above command line. Then you could use ‘--instance/-i” to specify which app instance you want to view.
$ az spring-cloud app log tail -g AzureSpringCloudDemo -s demo -n gateway

Command group 'spring-cloud' is in preview. It may be changed/removed in a future release.

Multiple app instances found:

gateway-default-7-7cc48cffbc-4kz56

gateway-default-7-7cc48cffbc-jwvb2

Please use '-i/--instance' parameter to specify the instance name

$ az spring-cloud app log tail -g AzureSpringCloudDemo -s demo -n gateway -i gateway-default-7-7cc48cffbc-jwvb2

Alert

Metrics for apps can be hooked up to alerts. Metric alerts evaluate at regular intervals to check if conditions on one or more metric time-series are true and notify you when the evaluations are met. For Azure Spring Cloud, you can define a metric alert rule by specifying a target app or app instance, metric name, metric condition and an action group to be triggered when the alert rule fires. Below is an example and you could get more details here.
  • Metric: Tomcat Request Average Time
  • Condition: Greater than 1000 milliseconds
  • Action: Email
 

CI/CD

Azure Spring Cloud supports both Jar artifacts and source code. If you want to automate the build and/or deployment, you could follow below guidance to set up a pipeline with the power of Azure CLI to deploy your changes automatically to Azure Spring Cloud. Github Actions / Azure DevOps / Jenkins We hope you enjoyed these announcements. Your feedback has been instrumental in shaping these features, keep the feedback coming. If you encounter any issues with Azure Spring Cloud, you could create an Azure Support Request. Our customer support team are standby to respond your issues ASAP.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.