Diagnostic Log Stream

Overview

One of the keys to diagnose the issues is to look at the trace files. Kudu service as well as its application write traces to Logfiles folder (see File structure on Azure). Logstream endpoint (/logstream) enables developers to view live traces as they happen in the system allowing the real-time diagnostics.

Using /logstream

If you are using git to push to an Azure Web Site, this is the section you'll care most about.

Version of Kudu currently live in Azure

• The changeset that's currently live in Azure is 94d69abe1cd0bc822635f0b4dc12e459fae4ef04

How-to guides

• Publishing a website with Git (official documentation ftom windowsazure.com)
• Customizing Deployments: choosing which folder or project to deploy to the web site
• Deployment branch: choosing the branch that gets deployed when you push
• Managing settings and secrets: how to modify the values when the app is deployed
• Managing database connections in Azure Web Sites
• Deployment hooks: how to take over the deployment logic for a site
• Accessing files via FTP

Understanding Kudu

• Kudu architecture
• REST API
• Enabling continuous deployment from Github, Codeplex and Bitbucket
• File structure on Azure
• Understanding deployment credentials
• How Kudu deploys sites

Troubleshooting

• Known issues
• Investigating Issues
• Diagnostic Log Stream

Building and running Kudu from the github sources

Read this is you are interested in contributing to Kudu

• Getting Started
• Blog post: Developing Kudu locally and on Azure
• Project Structure
• Running Tests
• Git workflow for contributors
• Coding Guidelines We use the coding guidelines used by AspNetWebStack

Features in development

• Deploying from GitHub
• Custom Deployment Script

Miscellaneous

• Blog posts and screencasts
• Cool user tweets