From a86b2719158b17441a6488a9900cc03f2388be36 Mon Sep 17 00:00:00 2001 From: Swede <70436002+swedeofenbound@users.noreply.github.com> Date: Sat, 6 Dec 2025 09:41:45 +0100 Subject: [PATCH 1/2] changed iis logs section in log-files.md added info on automatic reboots and restructured the block for reading flow --- .../log-files.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md index 5ae7aabceb9..0de824bc5e5 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md @@ -69,15 +69,17 @@ This will delete 90% of the oldest logs that are unread and leave you with 10% o ## IIS Logging -It is possible to enable IIS Logging on each of your Umbraco Cloud environments. There is a rolling size limit on the log files of 100 MB. This means that once the limit is reached, the oldest log files will be overwritten by new ones. +It is possible to enable IIS Logging on each of your Umbraco Cloud environments. You can enable the logging at **Settings --> Advanced** in the project overview for the project. -{% hint style="info" %} -The IIS logging will be automatically turned off after 12 hours. It's not possible to have them enabled for longer at once due to possible performance degradation while the logging is enabled. -{% endhint %} +The logs will be accessible from KUDU in `C:\home\LogFiles\http`. + +After enabling or disabling IIS logging for the environment, the site will reboot. + +### Limits -You can enable the logging from the **Advanced** menu found under _Settings_ in the project overview for the project. The logs will be accessible from KUDU in `C:\home\LogFiles\http`. +There is a rolling size limit on the log files of 100 MB. This means that once the limit is reached, the oldest log files will be overwritten by new ones. -After enabling IIS logging for the environment, the site will have to restart. +The IIS logging will be automatically turned off after 12 hours, also triggering a site reboot. Longer than 12h is not possible due to possible performance degradation. Find more information about IIS Logging on [the Official Microsoft Documentation](https://docs.microsoft.com/en-us/iis/configuration/system.webserver/httplogging). From 89a6ae6314c3e75a35c69ee2d0f0a5af6d3461b0 Mon Sep 17 00:00:00 2001 From: Swede <70436002+swedeofenbound@users.noreply.github.com> Date: Mon, 8 Dec 2025 09:50:11 +0100 Subject: [PATCH 2/2] Update umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md Co-authored-by: sofietoft --- .../resolve-issues-quickly-and-efficiently/log-files.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md index 0de824bc5e5..32002a7d7dd 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md @@ -69,7 +69,7 @@ This will delete 90% of the oldest logs that are unread and leave you with 10% o ## IIS Logging -It is possible to enable IIS Logging on each of your Umbraco Cloud environments. You can enable the logging at **Settings --> Advanced** in the project overview for the project. +It is possible to enable IIS Logging on each of your Umbraco Cloud environments. You can enable the logging at **Configuration --> Advanced** in the project overview for the project. The logs will be accessible from KUDU in `C:\home\LogFiles\http`.