Xref: number1.nntp.dca.giganews.com microsoft.public.cmserver.general:52502

We use Webtrends (log analyzer) to web statistics. After we migrated to MS
CMS, the Webtrends reports only show about a third of the actual activity
(visits, views, etc).  Not being a systems IT guy, I wondered if CMS was
caching requests away from the IIS logfiles so my reports (that use the IIS
logfiles) are now invalid. At the same time as the CMS install, ISA went in
as well so I had the same question about it. Any ideas?

[ Post a follow-up to this message ]

Unless you convert your log files from IIS, MCMS Urls will be in the
logfiles - Urls to cached elements rather than 'objects' within MCMS. This
will lead to inaccurate webtrends reports.

The IIS Log File Convertor
http://www.gotdotnet.com/Community/...97-A240C883EA9C
converts - /NR/rdonlyres/<GUID> into the Resource.Path equivalent. These
files are then ready for WebTrends.

Your ISA could also potentially effect your stats, ISA reports can (un)prove
this, but this is only true if it is a browse proxy/cache. ISA Web
Publishing will not affect your stats.

hth
Spence
www.mcmsfaq.com


"Dave H" <Dave H@discussions.microsoft.com> wrote in message
news:74D1FD19-DBCE-4620-8F9F-2409ECA96EC7@microsoft.com...
> We use Webtrends (log analyzer) to web statistics. After we migrated to MS
> CMS, the Webtrends reports only show about a third of the actual activity
> (visits, views, etc).  Not being a systems IT guy, I wondered if CMS was
> caching requests away from the IIS logfiles so my reports (that use the
> IIS
> logfiles) are now invalid. At the same time as the CMS install, ISA went
> in
> as well so I had the same question about it. Any ideas?

[ Post a follow-up to this message ]

In general, I've not seen the behavior your report.  IIS will dutifully
log requests for all MCMS postings, regardless of whether MCMS has
cached them (it's still a URL request), just as it would for ordinary
HTML pages.  The log converter, in this case, works well for resources
and pages in authoring mode, but I'm not sure it addresses the issue
here (although that may explain some of it).  How is ISA set up?  Are
you using it to cache pages on your web server to reduce traffic to
that environment?  Has anything else in your enviornment changed, like
using some other edge caching technology?  Also, what are you comparing
the current report to?  The prior site could have artificially inflated
the statistics and now you're simply seeing the "real" number.

More detail will help.

Shawn

[ Post a follow-up to this message ]