we have some profiles (log tracking enabled) with significant log
sources size (3 with approximately 1.2GB of data each one/day).

To save space the logs are stored bzip2ed, the problem is that each
time we run a profile with some new logs in order to update the
reports, Urchin uncompresses each log file to determine whether to use
it or not. Having on line logs from January 2009, this means that to
reach November logs Urchin needs hours of work.

The only solution that I've figured out is partitioning log sources on
monthly basis and use a script to change current log sources
associated to profiles, keeping only the most recent (this approach
can also prevent to meet the known bug about the number of physical
log files).

Is there a better way to solve the problem?

Thanks in advance,
Cristian

Yes, you should use date substitution so that Urchin will only read
log files from the previous day, instead of checking every file each
time it runs. See this article for more information:

http://www.urchintools.com/urchin6/configuration/log-sources

Kirk
www.urchintools.com
www.urchinexperts.com
www.actualmetrics.com

On Nov 13, 1:12 pm, Cristian Mezzetti <cristian.mezze...@gmail.com>
wrote:

If I understand correctly, with date substitution it's possibile to
configure a time slot as "the last day" (exYYMMDD*), "the last
month" (exYYMM*), ecc..
Is there a way to configure a slot like "the last 10 days"?

My worry is that on month change a processing error or log management
problem the last day, may cause to ignore some file logs if the next
run happens the next day(1st of month).

Anyway I'll start with this configuration.

Thanks,
Cristian

On 17 Nov, 17:59, Kirk - Actual Metrics <kirk.mora...@gmail.com>
wrote: