Your First Stop for SFCC Troubleshooting: WebDAV Logs

As an SFCC developer, when something breaks, my first stop is usually WebDAV in Business Manager. It holds everything—system logs, job logs, service logs, and of course error logs (both core and custom).

---

1. Finding the Right Log

1. In Business Manager, go to Administration → Site Development → Development Setup → Log Files → WebDAV
2. Drill into your site’s environment folder and grab the *-Error.log (or your custom log, e.g. custom-***.log).
3. Convert the customer’s bug timestamp to GMT—WebDAV timestamps are in UTC.

2. Why WebDAV Matters

• Zero setup: No extra installs or extensions required.
• Raw data: Get unfiltered .log files—perfect for grep, piping into scripts, or any custom tooling.

3. WebDAV’s Limitations

• 30-day retention Error logs are kept for 30 days. For other log-type retention periods, see the official docs.
• 10 MB/day cap Each server can write up to 10 MB per GMT day. Once the limit is hit, logging pauses until midnight UTC.
• Coverage gaps Not every code path is logged by default. Add Logger.error (or other Logger calls) in key try…catch blocks (e.g. order creation, payment callbacks) so you don’t miss vital errors.

---

Enhancing WebDAV with Demandware With Ease

When raw logs get unwieldy, the Demandware With Ease browser extension supercharges your WebDAV view:

• Color-coded directories by last-modified date
• File-size tags to spot bloated logs at a glance
• Tree vs. flat views for deep directory navigation

Learn more in the DWWithEase WebDAV docs.