Tracing in SDL Tridion 2013 SP1 - A walk in the park, or.. beach

Some time ago, a little birdie told me in SDL Tridion 2013 SP1, all windows services can be started in debug mode.

While I have not made the time to check this out, I have through experience and some focused searches discovered that tracing has been taken to yet another higher level.

Some of the logs below will be familiar from previous versions, however, there are a few surprises you won't mind finding out about.

Like a walk on the beach, where tracing back the same path you took to arrive where you are can be both nostalgic and new, here is a collection of traces to walk you from the Content Manager to the Content Delivery and back in case you need to revisit some points in time..

What	Where (log or trace file)	How (Config file & Steps)
CME Javascript/CSS	Browser Developer Tools (eg. Sources and Console tabs) IE Firefox Firebug Chrome	http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20full%20documentation-v1/GUID-9652A9DD-3E44-44ED-98C8-28A7FF955CA0 %TRIDION_HOME% WebRoot\Configuration\system.config 1. Disable JS/CSS minifiers <filters>     <filter for="Script" type="Tridion.Web.UI.Resources.Filters.JScriptMinifier, Tridion.Web.UI.Resources.Filters" enabled="never"> ... <filter for="Style" type="Tridion.Web.UI.Core.Configuration.Resources.Filtering.CssCompressorFilter, Tridion.Web.UI.Core" enabled="never" /> 2. Refresh browser 3. Can call GUI urls with mode=js 4. Check Sources, Console tabs in browser developer tools to set breakpoints and/or follow execution or variable values
IIS	%SystemDrive%\inetpub\logs\LogFiles\ <ID of Web site>	Usually enabled, if disabled, check how to enable depending on IIS version
CMS Events	%SystemRoot%\System32\Winevt\Logs\ Tridion.evtx %SystemRoot%\System32\Winevt\Logs\ Tridion Content Manager.evtx	Enabled by default, look for them in the Windows Event Viewer console
CMS Core Service	Own trace	%TRIDION_HOME%\bin\TcmServiceHost.exe.config http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20full%20documentation-v1/GUID-FE919074-22B4-4A00-BDB7-92EF0DC20C3C
CME Server Log / CMS WCF	%TRIDION_HOME%\web\WebUI\WebRoot\ Tridion.Web.trace	%TRIDION_HOME%\web\WebUI\WebRoot\bin\web.config http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20full%20documentation-v1/GUID-16AB0377-ECB7-4FCC-9EB3-128F75AF1E90
CMS Workflow Service	Own trace	%TRIDION_HOME%\bin\TcmWorkflowAgent.exe.config
CMS Search Indexer	Own trace	%TRIDION_HOME%\bin\TcmSearchIndexer.exe.config
CMS Batch Processor	Own trace	%TRIDION_HOME%\bin\TcmBatchProcessor.exe.config
CMS Publisher Service	TRIDION_HOME%\bin\TcmPublisher.exe.config Tridion.ContentManager.Publisher.log	To run publisher in debug mode from command line: not supported, not documented, unexpected results: dies when user running it logs off? -only to be done in Production envs under Customer Support request publisherpath>TcmPublisher.exe /debug ---------------- To have publisher log to file: - In MMC set "Publisher settings" - "Activate logging to publisher actions" option to "true", don't need to restart COM+ or Publisher - Check "c:\program files\tridion\log\Tridion.ContentManager.Publisher.log" - (It doesn't track when rendering in TemplateBuilder template tool) - Publisher log configurable in : \Tridion\bin\TcmPublisher.exe.config
CM Transport	c:\tridion\log\cd_transport_<date>.log	%TRIDION_HOME%\config\logback.xml <property name="log.level" value="ALL"/> or <property name="log.level" value="TRACE"/>
CD Transport	c:\tridion\log\cd_transport_<date>.log c:\tridion\log\cd_core_<date>.log	%TRIDION_DEPLOYER_HOME%\bin\config\logback.xml http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20full%20documentation-v1/GUID-DF88578C-8B32-4933-A6F5-939DA3275D95
CD Deployer	c:\tridion\log\cd_deployer_<date>.log c:\tridion\log\cd_core_<date>.log	Normal Trace and Hibernate Trace %TRIDION_DEPLOYER_HOME%\bin\config\logback.xml <property name="log.level" value="ALL"/> or <property name="log.level" value="TRACE"/> ----------------------------------------------------- <root level="ON">      <appender-ref ref="rollingCoreLog"/> </root>
OutBoundEmail	C:\Program Files (x86)\Tridion\Log\OutBoundEmail.log	%TRIDION_HOME%\config\OutboundEmail.xml <Log>         <Folder>C:\Program Files (x86)\Tridion\log</Folder>         <Level>5</Level> </Log>
UGC	%TRIDION_HOME%\web\WebUI\WebRoot\ Tridion.Web.Trace	1. Backup %TRIDION_HOME%\web\WebUI\WebRoot\Tridion.UGC.Model.dll 2. Replace with %TRIDION_HOME%\web\WebUI\WebRoot\trace\Tridion.UGC.Model.dll 3. Reset IIS

As with any logging in general, beware lots and lots of data will be accumulated in a very short amount of time.

So

- focus your actions

- limit the number of users in the system during tracing

- check there is enough memory available

- check there is enough storage available

and.. don't forget to turn off the traces when done investigating!

Happy tracing!