-
Notifications
You must be signed in to change notification settings - Fork 0
Diagnostic Log Stream
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 are being written allowing the real-time diagnostics.
By simply connecting to /logstream, you will be able to get the live streaming of traces. The /logstream watches all the files changes under /LogFiles and its sub folders. To scope the live traces to certain providers/folders, you may additional specify the path.
- /logstream/git/trace => kudu related traces intended for diagnostic kudu issues.
- /logstream/git/deployment => kudu deployment traces intended for application developers/operators.
- /logstream/application => application traces.
- /logstream/http => iis logs.
etc.
Most trace providers allow users to adjust the verbosity of the traces. Kudu trace provider uses Diagnostic's TraceLevel; Off=0 (default), Error=1, Warning=2, Info=3, Verbose=4. Its trace level can be adjusted via settings.
-
set kudu trace_level to Verbose.
$ curl <kudu-service-url>/settings -X POST -H "Content-Type: Application/json" -d "{'trace_level':'4'}" -
get kudu trace_level to Verbose.
$ curl <kudu-service-url>/settings/trace_level
By simply connecting to /logstream, you will be able to get the live streaming of traces. The /logstream watches all the files changes under /LogFiles and its sub folders. To scope the live traces to certain providers/folders, you may additional specify the path.
- The changeset that's currently live in Azure is 94d69abe1cd0bc822635f0b4dc12e459fae4ef04
- 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
- Kudu architecture
- REST API
- Enabling continuous deployment from Github, Codeplex and Bitbucket
- File structure on Azure
- Understanding deployment credentials
- How Kudu deploys sites
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