Advanced Scenarios in Azure Functions

Kudu

Your browser needs to be JavaScript capable to view this video

Try reloading this page, or reviewing your browser settings

This video segment demonstrates using Kudu with Azure Functions.

Keywords

  • Azure Functions
  • Azure
  • Development
  • Kudu

About this video

Author(s)
Sahil Malik
First online
20 December 2019
DOI
https://doi.org/10.1007/978-1-4842-4408-1_13
Online ISBN
978-1-4842-4408-1
Publisher
Apress
Copyright information
© Sahil Malik 2019

Video Transcript

Sahil Malik: A pretty amazing tool that is integrated with Azure Functions is Kudu. It really helps during development. Let’s look at it. Again with your function app selected, go to Platform Features, scroll down to the left here and you should see a section called Development Tools in which you see a link for Advanced tools Kudu. Go ahead and click on it. So it launches a URL that looks like this. Your-function-app-name.scm.azurewebsites.net. And it is protected by authentication, so it’s not like anybody on the internet can access it. But there is a wealth of information here.

So let’s click on Environment. You see that it shows me my entire environment. I mean this is like being on the IIS server, isn’t it? I can look at the app settings or deployments are there, source control info, what files are there, log streaming says “use curl, not browser” because logs get big so that’s what they prefer us to do. They want you to do that in a terminal. Processes and mini dumps, runtime versions, what extensions you have installed with which you can enhance the capabilities of your runtime, what webhooks you have, what functions you have. So I can click on here, it gives me a JSON output. Feel free to click on the other links as well. You’ll see similar JSON outputs. I can look at a debug console. The same command or PowerShell that I accessed from the platform features area, I can access that from Kudu as well.

What’s different though is it gives me this navigation U.I. at the top so I can go into cd logfiles. See this thing up here, it changes, right? And I can look at the log files here, like the eventlog.xml or I can download that. You see that it really makes development a lot more powerful. Let’s see what else is in here. So I have ASP.NET, SSH settings, data. Let’s go to the site area, so cd site. Let’s see what’s in here. There is deployments, diagnostics, locks, repository, wwwroot. Wwwroot is where I expect to see my code, and there is my code. You can do all this through Kudu. This is amazing.

There’s Process Explorer. I’ll show that in a moment but let’s dive to tools. Under tools, I can look at a diagnostic dump, a WebJobs dashboard, webhooks. I can even deploy a ZIP file directly from here. I can download a deployment script. So let’s look at a diagnostic dump for now and it downloads a dump here as a ZIP file. You can go ahead and open it and see what that looks like. So you see that Kudu is pretty amazing and in a serious project, I am sure that you’ll end up using this and find it very, very helpful.