Notification

Urchin WebAnalytics Software is discontinued and is no longer supported. All Urchin documentation applies only to the Urchin product as it was at the time of discontinuation, and does not apply to any Google Analytics products or services.

Why can't I use wildcards with remote (FTP or HTTP) log files?

Overview

Remote log files, such as those transferred via ftp or http during processing, cannot be configured using the same wildcard expressions available for local log files. However, it is possible to use a date-stamp expression, such as YYMMDD or YYYYMMDD.

Wildcards, such as *, allow Urchin to grab multiple files with one log file name entry. This is not available for remote logs for two reasons. First, it is very easy to inadvertently download entire filesystems with the standard FTP "mget" function. Second, the ftp/http routines are much more complex to manage if more than one file is being accessed at the same time.

Users should either download the remote logs before running Urchin (logs can be concatenated before doing so), or create a separate entry for each remote source. The YYMMDD syntax is available in remote log file specifications to allow automatic processing of remote logs that are on a rotation schedule.

See Also

  • Using YYMMDD or YYYYMMDD Syntax in Log Source File Name Specifications

  • Search
    Clear search
    Close search
    Main menu
    15659329050238933390
    true
    Search Help Center
    true
    true
    true
    false
    false