...
There may be times when one or more applications fail to fully start. This is usually due to an issue with the environment. In case of this happening, it may be useful to access the failing services' Web.Config files, and enable stdout logging. Please be very cautious when enabling this, as it doesn’t clean up after itself. Once the service is up and running anew, there’s a real threat of it filling the disk entirely.
Log server configuration
The log server exposes the following configuration options:
Option name | Description |
|---|---|
| The location of the log files on disk (Can be either a relative path, or absolute) |
| The size on MB for now large each individual log file is allowed to be (Roughly) |
| How many log old log files we keep around |
| How long we should keep error logs |
| How often we should run cleanup of error logs |
| What kind of storage we should use. Currently on “Local” is supported. |
All these settings can be changed on the fly, without requiring a restart of the LogServer process.