Products
Webtrends Analytics 9.x
Webtrends Analytics 8.x
Issue
Analysis runs nightly but, the reports only show data from one or more days ago, not yesterday’s data. There is no “task execution has failed” warning.
Resolution
This results from one of the reasons below:
1. The Analysis Throttling setting set to analyze only one day and the “Rerun analysis immediately after maximum amount of data is analyzed” option is unchecked. Analysis throttling is used to limit the amount of data Webtrends analyzes in a single pass and in this scenario it will only analyze one day’s worth of data before stopping and waiting for the next scheduled analysis. To enable this setting, edit the profile and select Analysis > Analysis Throttling. Check the box to rerun analysis immediately after the maximum amount of data is analyzed.
2. A date macro is in use. A date macro is a method of limiting the number of log files Webtrends looks at for analysis. Date macros are especially useful when the log file data source is an FTP data source path.In the Administration console, under Data Sources, confirm the data source in question does not contain an expression like %dd-1% in the log file path. The date macro in this example analyzes the previous day and disregards all data that came before it. Copy this line and change it to %dd% on the copied line so Webtrends looks at the present day’s log files. Note: you can have multiple date macro lines in a log file path box. Make sure they are sequential so no day is missed: %dd% on the first line, %dd-1% on the next, %dd-2% on the third, and so on.
3. A custom script is delivering the log files. Some people have firewall issues that prevent Webtrends from accessing the log files directly, so scripts are used to move the log files to a directory which Webtrends can access. In this case, Webtrends is working as intended and the scheduling of the script requires review.
4. Stalled events. When an analysis event enters the queue, it has eight hours to complete before Webtrends automatically cancels it. If all profiles are scheduled to analyze at the same time, the last profile to enter the queue can be “stalled” while it waits for all the other profiles to complete analysis. You will see Stalled events listed in the Alerts. The solution is to spread out all scheduled analysis events across the entire day.
5. Log file rotation rate. If SDC is being used, the log file will not be available until the log file rotation period has been reached. Log file rotation can be based on time or size. The entries in the log are stored in a file called dcsbusy until the rotation rate is reached. dcsbusy cannot be analyzed because it is locked by the SDC server. When the log file rotation period has been reached it will turn the dcsbusy into a log file that can be analyzed.
If this is the cause, then open the dcs.cfg file (located in \Webtrends\SmartSource Data Collector\cfg) on the SDC server and examine the settings in #Begin Log File Rotation Section. If servicemodel=true in the # Begin servicemodel Section at the bottom of the file, then the controlling entry will be rotationratestandardlag=. If you decide on any changes, the SDC will have to be restarted by opening a command prompt and running the command “iisreset” in order for changes to be applied.
If there is an error in the current status column, then there may be issues with analysis. If it says completed successfully, then chances are the program working as expected but configuration changes need to be made to keep report data current.