Just to throw in another idea. If you are using the below solution with webtrends
and creating your own log files.
You could create a redirect script as part of your error script that
would redirect the Webtrends Friendly URL's
back to the right pages on your site. That way you get all the reverse lookup
information. The only thing that
creating your own logs won't give you is the images information But
unless you are tracking your images that won't matter.
Just another Idea.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 2:25
PM
To: [EMAIL PROTECTED]
Subject: RE: FuseBox Logs: (RE:
Web Trends FB)
I also had this problem
when I first started coding fusebox applications. I spent a few weeks trying to
find ways around it and the solution I ended up with was to turn off IIS
logging and write my own custom log application. I call the tag in app_globals
and using cffile basically emulate the log file that IIS creates except
that I replace index.cfm with the fuseaction being called. The only
downfall that I had was that the links didn't work from within webtrends...but
whatever - as long as my clients had accurate information on what pages were
being called they were happy. I've also been monitoring the sites to see if
there was any noticeable slow downs and for the most part it only added about
20ms to the page processing time.
-----Original Message-----
From: Jeremy Ridout
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 9:24
AM
To: '[EMAIL PROTECTED]'
Subject: RE: FuseBox Logs: (RE:
Web Trends FB)
I had the same
problem a few years ago using the original formURL2Attributes tag. The fact of
the matter is that IIS logs (at least IIS4) do not record anything after the
"index.cfm". If there is a "?" then that information is
stored in a different location in the log file. Since the SES urls do not have
a ?, IIS ignores that information.
This is not a
problem with Webtrends, it's an IIS thing. I tried several ways of dealing with
this including logging to a database, creating my own log file, etc. But
Webtrends then had problems. It became too much of a hassle to try and make my
log files into a format that Webtrends could understand. So I gave up.
I dislike the
idea of making my own usage statistics generator. There just isn't enough time
in the day to create all of the different reports that I or my coworkers
want/need. Webtrends has built an entire, successful business doing just
that... Ill stick with them.
I ended up
going with a URL that IIS could understand, my URLs are not FB standard
(and my site is not yet FB3), but basically, the URL looks like: http://www.acep.org/1,242,0.html.
This allows me to pass the page ID and I built a simple parser in the index
page to figure out what is going on. IIS is happy, Webtrends is happy. FB is
not, but it could be with a little extra effort.
Cold Fusion MX
changed a few things and offers some exciting new possibilities of
expanding this method and Im currently working on an article and tag that will
illustrate this.
-----Original Message-----
From: Roger Dahlstrom
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 9:55
AM
To: '[EMAIL PROTECTED]'
Subject: RE: FuseBox Logs: (RE:
Web Trends FB)
I think I was able to get
Webtrends to recognize query strings - it's something like a "watch
list" or something to that effect. The crappy thing was that I had
to manually add just about every permutation to it in order to make it
work.
-----Original Message-----
From: Robert Everland
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 10:45
AM
To: '[EMAIL PROTECTED]'
Subject: RE: FuseBox Logs: (RE:
Web Trends FB)
If I was going to turn it
off and do that, I may as well let it go and write a parser that will do it for
me, that way I have all of that information. The sales and marketing team
here love webtrends and I am making our website into fusebox so that the code
is easier to manage, now when I deliver them log reports they will ask me why
everything goes to this file. It's gonna be a mess.
Robert Everland III
Dixon Ticonderoga
Web Developer Extraordinaire
-----Original Message-----
From: Roger Dahlstrom
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 10:49
AM
To: '[EMAIL PROTECTED]'
Subject: RE: FuseBox Logs: (RE:
Web Trends FB)
I'm thinking that you
could disable the logging from IIS, and just write a log file yourself - to
text. You won't get the image downloads and stuff, but just about
everything else you can get. Then Webtrends can do all the resolution,
search engine parsing, etc. Could work.
-----Original Message-----
From: Robert Everland [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 10:05
AM
To: '[EMAIL PROTECTED]'
Subject: RE: FuseBox Logs: (RE:
Web Trends FB)
I looked at steve's and
it just doesn't report as much as web trends does, if it did I would buy it and
use it in a second, but I just can't, I also would be a bit hesitant to put
something like that on a high profile site as even microsoft has said that they
do not recomend logging to a database as it slows performance. I would really
love it if I could get web trends to work right with fusebox, that is the only
issue I have with fusebox right now.
Robert Everland III
Dixon Ticonderoga
Web Developer Extraordinaire
-----Original Message-----
From: Josh Carrico
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 10:01
AM
To: [EMAIL PROTECTED]
Subject: FuseBox Logs: (RE: Web
Trends FB)
Have you seen Steve's
FuseBox Logs?
I'm running on a
semi-high traffic site receiving aprox. 32000 unique session a month.
Only problem was cutting
a record for each click per user, but I did some tweaking to fix that right
up.
I added a log
repository to track user footsteps, as well as top page views.
-----Original Message-----
From: Roger Dahlstrom [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 9:43
AM
To: '[EMAIL PROTECTED]'
Subject: RE: Web Trends
Hmmm. I suppose you
could write to a text file in the IIS log format if you wanted - you could turn
off logging from IIS and just write your own text file. That would
probably work.
-----Original Message-----
From: Gallant, Ron
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 9:25
AM
To: '[EMAIL PROTECTED]'
Subject: RE: Web Trends
Well my company uses
webtrends, we just kinda plug into that. Not a whole lot of options. other then
scratching FB3. Yah right. lol
-----Original Message-----
From: Roger Dahlstrom
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 9:20
AM
To: '[EMAIL PROTECTED]'
Subject: RE: Web Trends
Nope. The problem
(at least in my case) is that IIS does not log anything past index.cfm, so
there's really no way for WebTrends to do anything with it. What I have
done is the following (Michael, this will help you with your long-running
requests as well).
Create a table with the
columns that I want - I use date/time, IP, Request Method, Requested Page, HTTP
Status, Time Taken, User Agent, HTTP Referer, and User Cookies, but any CGI
variable will work. This doesn't log any images - just pages, and just
those that come from index.cfm (in my case at least, that's all I use).
In that file, the Requested Page is #server_name##path_info##query_string#, and
I use getTickCount() to log the request time taken.
-----Original Message-----
From: Gallant, Ron
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 8:04
AM
To: '[EMAIL PROTECTED]'
Subject: Web Trends
Has anyone found a way to
get Web Trends to recognize FB3 pages? I am using SES urls and all web trends
is showing is allot of hits to index.cfm.
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this e-mail
message. Any personal comments made in this e-mail do not reflect the views of
Blue Cross Blue Shield of Florida, Inc.
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this e-mail
message. Any personal comments made in this e-mail do not reflect the views of
Blue Cross Blue Shield of Florida, Inc.
==^================================================================ This email was sent to: [EMAIL PROTECTED] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV6CfY Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
|
