App Service diagnostics and logging in Azure - Mini Project: Build & Apply

App Service Diagnostics and Logging Setup

📖 Scenario: You are managing a web application hosted on Azure App Service. To keep the app healthy and troubleshoot issues quickly, you need to set up diagnostics and logging.This project will guide you through enabling application logging, setting a log retention period, and viewing the logs.

🎯 Goal: Enable application diagnostics logging on an Azure App Service, configure log retention, and display the log file path.

📋 What You'll Learn

Create a variable with the App Service name

Create a variable with the resource group name

Enable application logging to file system

Set the log retention period to 7 days

Print the path where logs are stored

💡 Why This Matters

🌍 Real World

Setting up diagnostics and logging is essential for monitoring and troubleshooting web applications running on Azure App Service.

💼 Career

DevOps engineers and cloud administrators often configure logging to maintain application health and quickly resolve issues.

1

Set up App Service and Resource Group variables

Create two variables: app_service_name with the value "myappservice123" and resource_group with the value "myresourcegroup".

Azure

# Create variables for app service and resource group
# Your code here

Hint

Use simple assignment statements to create the variables with exact names and values.

2

Enable application logging to file system

Create a variable called enable_logging_command that contains the Azure CLI command string to enable application logging to the file system for the app service named app_service_name in the resource group resource_group.

Azure

app_service_name = "myappservice123"
resource_group = "myresourcegroup"
# Create enable_logging_command with Azure CLI command string
# Your code here

Hint

Use an f-string to insert the variables into the Azure CLI command that enables application logging to the file system.

3

Set log retention period to 7 days

Create a variable called set_retention_command that contains the Azure CLI command string to set the log retention period to 7 days for the app service named app_service_name in the resource group resource_group.

Azure

app_service_name = "myappservice123"
resource_group = "myresourcegroup"
enable_logging_command = f"az webapp log config --name {app_service_name} --resource-group {resource_group} --application-logging filesystem --level Information"
# Create set_retention_command with Azure CLI command string
# Your code here

Hint

Use an f-string to create the Azure CLI command that sets log retention to 7 days.

4

Print the log file path

Print the exact string "Logs are stored in /LogFiles/Application/" to show where the logs are saved on the App Service.

Azure

app_service_name = "myappservice123"
resource_group = "myresourcegroup"
enable_logging_command = f"az webapp log config --name {app_service_name} --resource-group {resource_group} --application-logging filesystem --level Information"
set_retention_command = f"az webapp log config --name {app_service_name} --resource-group {resource_group} --retention-days 7"
# Print the log file path below
# Your code here

Hint

Use a print statement with the exact string to show the log location.

Practice

1. What is the main purpose of enabling diagnostics and logging in Azure App Service?

easy

A. To increase the app's performance automatically

B. To monitor and troubleshoot the app's behavior and errors

C. To deploy new versions of the app faster

D. To secure the app from unauthorized access

Solution

1. Step 1: Understand diagnostics and logging purpose

   Diagnostics and logging help capture app events and errors for monitoring.

2. Step 2: Identify the main goal

   The main goal is to see what happens inside the app to fix issues.

3. Final Answer:

   To monitor and troubleshoot the app's behavior and errors -> Option B

4. Quick Check:

   Diagnostics = Monitor & troubleshoot [OK]

Hint: Think: Why watch app logs? To find and fix problems [OK]

Common Mistakes:

• Confusing logging with performance tuning
• Thinking logging deploys app updates
• Assuming logging secures the app

2. Which Azure CLI command correctly enables application logging for an App Service named myapp with file system logging?

easy

A. az webapp log config --name myapp --resource-group mygroup --application-logging filesystem --level Information

B. az webapp log enable --name myapp --resource-group mygroup --application-logging filesystem

C. az appservice log config --app myapp --group mygroup --enable-logging filesystem

D. az webapp logging config --app myapp --resource-group mygroup --log-type filesystem

Solution

1. Step 1: Identify correct Azure CLI syntax for logging

   The correct command uses az webapp log config with parameters for name, resource group, logging type, and level.

2. Step 2: Match command to options

   az webapp log config --name myapp --resource-group mygroup --application-logging filesystem --level Information matches the correct syntax and parameters exactly.

3. Final Answer:

   az webapp log config --name myapp --resource-group mygroup --application-logging filesystem --level Information -> Option A

4. Quick Check:

   Correct CLI syntax = az webapp log config --name myapp --resource-group mygroup --application-logging filesystem --level Information [OK]

Hint: Use 'az webapp log config' with --application-logging and --level [OK]

Common Mistakes:

• Using wrong command like 'az webapp log enable'
• Mixing parameter names like --app instead of --name
• Omitting the logging level parameter

3. Given the command az webapp log tail --name myapp --resource-group mygroup, what will be the output?

medium

A. It streams the live application logs from the App Service named myapp

B. It shows the last 10 deployment logs for myapp

C. It enables logging for the app myapp

D. It downloads the log files to local machine

Solution

1. Step 1: Understand the purpose of 'az webapp log tail'

   This command streams live logs from the running app in real time.

2. Step 2: Compare options to command behavior

   It streams the live application logs from the App Service named myapp correctly describes live log streaming, others describe different actions.

3. Final Answer:

   It streams the live application logs from the App Service named myapp -> Option A

4. Quick Check:

   Log tail = live streaming logs [OK]

Hint: Remember 'log tail' means live log streaming [OK]

Common Mistakes:

• Thinking it shows deployment logs only
• Confusing enabling logs with streaming logs
• Assuming it downloads logs instead of streaming

4. You ran az webapp log config --name myapp --resource-group mygroup --application-logging filesystem --level Error but logs are not appearing. What is a likely cause?

medium

A. The app is not generating any error logs to capture

B. The command syntax is incorrect and did not apply settings

C. The resource group name is invalid

D. You forgot to enable web server logging separately

Solution

1. Step 1: Check if web server logging is required

   Application logging and web server logging are separate; enabling one does not enable the other.

2. Step 2: Identify missing step

   If web server logs are needed, they must be enabled explicitly; otherwise logs may not appear.

3. Final Answer:

   You forgot to enable web server logging separately -> Option D

4. Quick Check:

   Separate enable for web server logs needed [OK]

Hint: Enable both app and web server logging to see all logs [OK]

Common Mistakes:

• Assuming application logging alone shows all logs
• Ignoring separate logging types in Azure App Service
• Blaming command syntax without checking logs generated

5. You want to diagnose a performance issue in your Azure App Service. Which combination of logging and diagnostic features should you enable to get detailed error messages, HTTP request logs, and live monitoring?

hard

A. Enable only detailed error messages without any logging

B. Enable only application logging to blob storage and disable web server logging

C. Enable application logging (filesystem), web server logging, and use az webapp log tail for live streaming

D. Use az webapp log download without enabling any logging

Solution

1. Step 1: Identify needed logs for performance diagnosis

   Detailed error messages, HTTP request logs, and live monitoring require application logging, web server logging, and live log streaming.

2. Step 2: Match features to options

   Enable application logging (filesystem), web server logging, and use az webapp log tail for live streaming enables all needed logs and live streaming for real-time diagnosis.

3. Final Answer:

   Enable application logging (filesystem), web server logging, and use az webapp log tail for live streaming -> Option C

4. Quick Check:

   Combine logs + live tail for full diagnosis [OK]

Hint: Combine app + web server logs with live tail for best insight [OK]

Common Mistakes:

• Relying on only one type of logging
• Not using live log streaming for real-time issues
• Downloading logs without enabling logging first