Self-service Data Alerts in SSRS 2012 - Learning SQL Server Reporting Services 2012 - page 396

You can enable the ones you want logged here as shown for Power View and
Reporting Server Alerting Runtime . At the bottom of this page you can configure
the following as well:
• Enable event log flood protection to detect repeating events in
Windows events
• Find the trace log path in the filesystem
• Number of days to store trace logs
• Restrict trace log disk space
One of the problems you may run into is that the logs are created
incessantly unless you take action as shown before to restrict the
frequency with which these files (these are hefty!) are written to
your filesystem. Also, these files are usually very large. Keep a
watch on this folder here:
C:\Program Files\Common Files\Microsoft Shared\
Web Server Extensions\14\LOGS
You may keep the more recent and get rid of the older ones. The default says you can
keep it for 14 days, but you can change this default. In any case, it is not necessary to
keep all of them.
Using PowerShell to review the logfile
The log file contains many categories and you can filter them with the following
PowerShell (this will be described fully in Chapter 8 , Reporting Services and
Programming ) cmdlet:
Get-content -path "C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\14\LOGS\Hodentekwin7-20130505-1506.log" | select-string
"sql server reporting services
The log file was created on May 5, 2013 and PowerShell filters the log file for SQL
Server Reporting Services. This is very useful when you want to find a pin in a
haystack. A sample output is shown here:
/--Sample result of running the above code--/
PS C:\Users\mysorian> Get-content -path "C:\Program Files\
Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\
Hodentekwin7-20130505-1506.log" | select-s
tring "sql server reporting services"