This article covers frequenly asked questions regarding LiveStats web statistics analyzer. For detailed infromtaion on LiveStats usage refer to the following documents: LiveStats.XSP 7: Getting Started with the Reports + Reporting Interface Guide + Web Site Settings Interface Guide, LiveStats 6: Reports User Guide, LiveStats 5: Report Interface

  • Averaged and forecast values in LiveStats.XSP reports

Averages and forecasts are calculated historically to any degree of accuracy after 3 full months have elapsed. Before that we do not troubleshoot issues with them as they are related to a short sample.

According to LiveStats documentation, the math behind the forecast is not public information but it is based on historical averages. If it sees that a Monday average was 10 and it’s been on the rise it will report something slightly above 10 as the forecast.

  • Why does LiveStats report that I have a welcome.htm page when I do not?

By default, LiveStats sets the default page for your directories to welcome.htm. This means that any time the site or a directory within the site is accessed without specifying the exact file name, LiveStats reports that welcome.htm was the page that was visited.

If you would prefer that LiveStats report the actual default document, please send a formal request to Technical Support and ask them to modify this setting. Please note that this setting is applied to all directories on your site, so if your directories do not all use the same default document, LiveStats will still only report the page name that has been specified. This change will be applied to all new reports and views, but your historical data will still show the original welcome.htm page.

  • Why do reports show visitors IP address, but not a domain name or geographical location?

Resolving IP addresses to domain names or geographical locations requires reverse DNS lookup which takes large amount of time along with the system resources. Running a single report will take hours. Also, it can slow the server down to non-responding to other requests on the large logs.

You can download raw log files and run reporting on it locally to get desired report information.

Note: the above is true for LiveStats version 5 and 6. LiveStats.XSP is able to resolve the IP addresses and display the geographical location.

  • How do I filter out virus worm attempts from my reports?

Rest assured, Intermedia installs security fixes from Microsoft as soon as they become available, protecting your web server from attempts by Internet virus worms to break in and infest your web site.

However, these attempts will show up in your LiveStats report in great number, obscuring the actual statistics of visits to your page.

For LiveStats 5 users: log into LiveStats and go to the Virtual Admin. Expand "Content Management," then expand "Create New Content Manager" and expand "New URL Manager." Enter the URL mask to filter --- for example, enter *cmd.exe* or *root.exe* to block all attempts to access any URL with "cmd.exe" or "root.exe". (The wildcard * matches multiple occurrences of any character, and ? matches exactly one occurrence of any character.) Select "Exclude matching URLs from statistics" and click "Submit Update."

A list of all filtered patterns appears in the Virtual Admin under Content Management > All Configured Managers.

  • How do I use Client Exclusions?

The Client exclusions section of LiveStats.XSP offers two features. Although these two features have very similar names, their purposes are very different.

The first, Client IP Exclusions is for excluding the IP addresses of visitors. This prevents traffic from your developers or administrators from showing up in the reports. You can specify an IP address range in this box by using wildcards in place of the last number. For example, you might put 255.255.255.*.

The second, Referral Exclusions is for excluding referers. This is where LiveStats wants you to put aliases that your web site might use. This prevents your web site from showing up as the number one referrer. For example, www.yourdomain.name, as well as your web site's IP address, should be placed here.

  • How do I get separate statistics for two domains on the same account?

Unfortunately, it is not really possible to separate out statistics for two domains hosted on the same account. This is due to the way log files work. Log files record what files/folders are opened, how they are opened, and where they are opened from. They do not record the domain name used to open a file. Therefore, it is not possible for any log parser to obtain this information (since it isn't in the log files).

If you need separate statistics for a site, there are several options offered in LiveStats.XSP:

  1. Set up a ChangeDetect. This is the most economical solution, and provides enough information for most purposes. Please note that this really only works if you host the content for two domains in two different directories. For example, if you host the content of domain.one in the /one directory (http://www.domain.one/one or D:\FTP\username\Htdocs\one), then you would set up a ChangeDetect for "/one". This watch would record all traffic that came to the /one directory. You can set up as many watches as you have directories. They are free. Watches don't provide as much information as the site-wide reports, so if you need that level of information, this solution will not work for you.
  2. Create Content Groups and add files that belong to different domains to corresponding content groups. You can use this tool even if you do not host the domains in separate folders. Although they do have to point to different pages.
  3. Move one of the domain names to another account. This is expensive, because you must pay for two accounts, and it may result in downtime of mail for the domain you move.
  4. Download raw log files and parse them locally using the statistics software of your choice. Most likely, that software will also require that the content of the sites be in different directories. However, it may be able to provide you with more details than the LiveStats ChangeDetect.