J.E. on 6 September 2001 has this to say about WebTrends:

A few weeks ago there was a conversation on the list about the WebTrends Log Analyzer (WTLA) product (now sold by NetIQ). It so happens that I have to acquire a log analysis system for a client, and I was going to simply purchase WTLA.

However, there may be a bit of a problem, which may necessitate me using a different package. ...

When I first bought it, WTLA was in version 4.5. It cost less than $200 and allowed me to run on one machine, and generate logs for up to 50 domains.

As of version 6, the terms are approaching UNACCEPTABLE. Here is a short list or my biggest gripes:

• List price now ~$900.
• Still only installed on one machine, still only for 50 domains.
• Additional limitation to analyzing logs generated from ONE PHYSICAL WEB SERVER.
• Reports or report-generated data CANNOT BE DISTRIBUTED OR VIEWED OUTSIDE THE ORGANIZATION. (Whoa... get sued for making a press-release?)
• NetIQ retains the ability to AUDIT your organization up to once per year. They can, with 15 days notice, come into your place of business, interview your staff, view the contents of your servers and backups and survey all the systems which are connected (or assumed to be connected) to their product.

These limitations are not based on the capabilities of the software. They are, by and large, only LEGAL limitations, which makes them even more distasteful. For instance, I can technically use the product to analyze logs from any number of servers, but NetIQ attempts to limit me legally.

...

Personally, I am so steamed about this I am ready to write a furious letter to their CEO. This is absurd, particularly because Log Analyzer is a GOOD PRODUCT, but IT AIN'T ORACLE. It's just a simple log analysis package -- nothing more. They need to get over themselves before they are stomped out of business by an upstart product.

This mirrors what we've seen with Log Analysis programs - they have increased in price and restrictions. Makes you want to check out the free, open source packages on the Log Analysis page, doesn't it?