App Service diagnostics and logging in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable application logging in Azure App Service using Azure CLI.

Azure

az webapp log config --name myApp --resource-group myResourceGroup --application-logging [1]

Drag options to blanks, or click blank then click option'

Ablob

Boff

Cfilesystem

Dconsole

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'off' disables logging.

Choosing 'blob' requires additional configuration.

Choosing 'console' is not a valid option here.

Using filesystem enables application logging to the file system in Azure App Service.

2fill in blank

medium

Complete the code to enable detailed error messages for your Azure App Service.

Azure

az webapp log config --name myApp --resource-group myResourceGroup --detailed-error-messages [1]

Drag options to blanks, or click blank then click option'

Adisable

Btrue

Cfalse

Denable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'false' disables detailed error messages.

Using 'disable' or 'enable' are not valid boolean values here.

Setting true enables detailed error messages in Azure App Service logs.

3fill in blank

hard

Fix the error in the command to stream logs from an Azure App Service.

Azure

az webapp log [1] --name myApp --resource-group myResourceGroup

Drag options to blanks, or click blank then click option'

Adownload

Blist

Cshow

Dtail

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'download' downloads logs but does not stream.

Using 'show' or 'list' do not stream logs live.

The tail command streams live logs from the Azure App Service.

4fill in blank

hard

Fill both blanks to configure web server logging to blob storage with a retention period of 7 days.

Azure

az webapp log config --name myApp --resource-group myResourceGroup --web-server-logging [1] --retention-period [2]

Drag options to blanks, or click blank then click option'

Ablob

Bfilesystem

C7

D30

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'filesystem' stores logs locally, not in blob storage.

Setting retention to 30 days is not what the question asks.

Setting blob enables logging to Azure Blob Storage, and 7 sets retention to 7 days.

5fill in blank

hard

Fill all three blanks to create a diagnostic setting that sends logs to a storage account, event hub, and log analytics workspace.

Azure

az monitor diagnostic-settings create --name myDiagSetting --resource /subscriptions/123/resourceGroups/myResourceGroup/providers/Microsoft.Web/sites/myApp --storage-account [1] --event-hub-namespace [2] --workspace [3]

Drag options to blanks, or click blank then click option'

Amystorageaccount

Bmyeventhub

Cmyloganalytics

Dmyresourcegroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource group name instead of storage account or event hub.

Mixing up the order of resource names.

These are the names of the storage account, event hub, and log analytics workspace to send diagnostics data.

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