1. Home
  2. Training Library
  3. Microsoft Azure
  4. Courses
  5. Getting Started with Azure App Service

Diagnostics

Contents

keyboard_tab
Introduction & Overview
1
Introduction
PREVIEW2m
Diagnostics
API Documentation
Mobile Apps
14
Deployment Slots
Course Summary
20
Summary
2m 29s

The course is part of these learning paths

AZ-303 Exam Preparation: Technologies for Microsoft Azure Architects
course-steps
29
certification
9
lab-steps
13
description
1
AZ-104 Exam Preparation: Microsoft Azure Administrator
course-steps
20
certification
6
lab-steps
16
more_horizSee 3 more
play-arrow
Start course
Overview
DifficultyBeginner
Duration1h
Students839
Ratings
3.5/5
starstarstarstar-halfstar-border

Description

You’ve got an idea for a great web app, or maybe you’ve already started building it. The next question is how are you going to get it out there on the Internet?

In this course, you will learn how you can quickly and easily set up a website and publish your app to the world with Azure App Service. Of course, web apps are a lot more complex and varied than just HTML pages and we will see how App Service supports a range of programming languages, frameworks, and even operating systems. We will explore features that greatly simplify application deployment and management, as well as those that will increase your app’s functionality like authentication and accessing on-premise data. App Service as with other Azure products has a raft of tools for monitoring and logging so you can make sure your app is performing optimally.

For any feedback, queries, or suggestions relating to this course, please contact us at support@cloudacademy.com.

Learning Objectives

  • Deploy apps using the Azure App Service
  • Create a web app using the Azure Portal
  • Create a web app using Visual Studio
  • Understand the configuration and diagnostic capabilities available from Azure App Service
  • Understand the advanced features of the service such as container deployment and deployment slots

Intended Audience

This is a beginner level course suited developers or anyone wanting to know how to deploy web apps to the Azure cloud.

Prerequisites

To get the most from this course, you should have a basic understanding of the software development lifecycle, while knowing how to code would be a plus.

Course source code

Visual 2019 with .NET Core 3.1 was used for the demonstrations in this course.

https://github.com/cloudacademy/azure-get-started-app-service.git

 

 

 

Transcript

It turns out that we don’t live in a perfect world and not everything goes as planned and nowhere is this truer than in the realm of software. We saw the remote debugging switch in general settings, but what about recording your app’s behavior while in action? Azure App Service provides a number of features that allow you to record, examine and be notified of particular events based on custom-defined rules. I’m going to take a detailed look at App Service logs, metrics and alerts.

Not only are App Service Logs a flexible way to collect a lot of information, but they also give you a couple of options in terms of digesting that data. We can collect different types of data as app logs, server logs, error messages, and failed requests. We can specify the level detail in those logs from error, warning, information through to verbose. We can say where we want the logs saved. I’m going to ask for verbose application logging with detailed error messages and failed requests saved to the file system. Before I start hitting the web app I’m going to change the connection string. After inducing a 404 and 500 errors let’s download the logs and have a look. To download the logs go to your web app URL with “scm” inserted before azurewebsites followed by /api/dump. This will download a compressed zip file of the logs. There are lots to look at here but I’ll just quickly dive into the detailed errors. If I go to Diagnostic settings I can specify the types of logs I want to send to a destination. Here I’ve said send Http logs and app logs to log analytics. Also, I can save logs to blob storage and specify that I only want to retain those logs for 7 days.

The Logs page will let you run queries on the logs to extract and summarize data into more easily digestible information. The IntelliSense in the log query function is very good. If you don’t know exactly what to look for just double click one of the logs to put it in the query window and then hit the run button. A log query is kind of like a SQL query except it starts with the table name without the keyword from and each clause is separated by the pipe character. Here you see summarize is analogous to SQL group by. You also have the ability to view your results as a chart instead of a table.

About the Author

Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a  Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.