Overall reports

Avatar
  • updated
  • Answered
I am trying the enterprise trial edition.
I am working on two log files.
I analyze one log file and see the report just fine.
when I analyze the second log file all the stats from the first one disappear.

is it because of the trial version?
Avatar
Michael
If you need to get report on both log files, you need to specify both of them in the profile properties.

The best way to analyze multiple logs at once is to specify a wildcard like c:\Logs\*.log instead of log file name in the profile properties. However, if you wish to analyze just two files from a folder with multiple files, you can either specify two file names separated by semicolon (e.g. "c:\Logs\1.log; c:\Logs\2.log" - without quotes), or choose the "Multiple" log location mode an specify each log file as a separate location.
Avatar
Benny
I know about these options but I am trying to simulate real life server.
In real life there is a new log file every day and I'll need to run analyze every day to see the added hits. just like awstats for example.

Is that even possible with this program?
Avatar
Michael
It's not possible, the program can show report on existing files only. However, it doesn't need to reanalyze old log files, it just checks that they exist and haven't changed, and then analyzes new log files and appends results to the database.
Avatar
Benny
well I tried that now but still does not work.
only the first file gets analyzed every time.
not even when I use wildcards.
Avatar
Michael
Does the program show that it analyzes both log files in the progress dialog? You can recheck it by clearing the analysis cache for this profile in Profile Properties > General (so the program will have to reanalyze the file).

You should also check your time range settings in Profile Properties > Time Range, maybe data from the second log is excluded because of these settings.
Avatar
Benny
well the time range wasn't all activity and now the program analyzes the two log files together.

Now the thing is that you said the program checks if a log file has been analyzed and doesn;t analyze it again.

it doesn't seem like that from the time it takes to analyze the two files after adding the second log file.
Avatar
Michael
The program needs to reanalyze both logs if you changed time range settings or any other settings (including file names in the profile properties).

In most cases the program should be set to analyze multiple logs by wildcard, e.g. C:\Logs\*.log. If there is one log file (e.g. 1.log), the program just analyzes it. If you create another log file (e.g. 2.log) to this folder, the program first checks that file 1.log exists and hasn't changed, and then analyzes file 2.log and appends results to the database.

You can find more information on how it works at http://www.weblogexpert.com/help/wlex...
Avatar
Benny
I guess I am confused with the time it takes to create the report which seems longer than the time to analyze my small log files..

anyway I think there should be an option to remember old data analyzed without the need to keep the raw log files in the directory.
it seems almost impossible to keep data for more than a year.
Avatar
Michael
Creating static (HTML/PDF) reports may require more time then analyzing small logs, while you can view if the program analyzes logs or creates a report in the progress dialog to estimate analysis time.

We considered adding support for using log cache as an archive with ability to delete old log files but decided not to implement this feature. The main problem is that the program is very customizable and supports a lot of settings that affect analysis results. E.g. it is possible to modify predefined report tables in the program options or create new filters in the profile properties. If any of such settings is changed, WebLog Expert needs to reanalyze all the log files to create a new report, it cannot just use an existing database. So it is still necessary to keep old log files in this case. And as log files should be kept anyway, we decided to always generate reports for existing log files only to avoid confusion.