Re: [analog-help] How do I Include pages with specific URL parameters?

2009-11-04 Thread Troy Simpson
Possible Solution:

I don't understand why yet, but this appears to get me closer to what I want.

ALL OFF
ALLCHART OFF
REQUEST ON  # Enable the Request Report
REQCOLS NRr # Enable these three columns in the report

# The following lines is a sample of the lines included via a
CONFIGFILE directive (232 in all).
FILEINCLUDE /*?*035E592F-FA2A-267B-5AF64F16D156031F
FILEINCLUDE /*?*03DA02E6-FF9C-FE0B-37856AF28E60357A
FILEINCLUDE /*?*03DA0008-F3ED-1110-1AB00948167C27F2
FILEINCLUDE /*?*03D9FE43-BCE3-8680-163785D70C2B83FF
FILEINCLUDE /*?*03D9FCBC-9E27-9E66-BD24D89F3463E89F
FILEINCLUDE /*?*03D9FB16-B382-47B9-1A1538C833BA0EAB
FILEINCLUDE /*?*03D9F9AF-A665-0FFE-4429F3C56B4B5AB2
FILEINCLUDE /*?*035E5920-BCA0-D364-936C15CC46CC409A
etc.

REQFLOOR 1r
REQARGSFLOOR 1r
REQINCLUDE /*  # This line was important.  But I am not sure why.  The
Request Report would return 0 request with out this line.

# The following lines are a sample of thelines included via a
CONFIGFILE directive (232 lines in all).
REQALIAS REGEXPI:035E592F-FA2A-267B-5AF64F16D156031F [Page Title Here]
REQALIAS REGEXPI:03DA02E6-FF9C-FE0B-37856AF28E60357A [Page Title Here]
REQALIAS REGEXPI:03DA0008-F3ED-1110-1AB00948167C27F2 [Page Title Here]
REQALIAS REGEXPI:03D9FE43-BCE3-8680-163785D70C2B83FF [Page Title Here]
REQALIAS REGEXPI:03D9FCBC-9E27-9E66-BD24D89F3463E89F [Page Title Here]
REQALIAS REGEXPI:03D9FB16-B382-47B9-1A1538C833BA0EAB [Page Title Here]
REQALIAS REGEXPI:03D9F9AF-A665-0FFE-4429F3C56B4B5AB2 [Page Title Here]
REQALIAS REGEXPI:035E5920-BCA0-D364-936C15CC46CC409A [Page Title Here]
REQALIAS REGEXPI:03D9D2CE-C4B3-8BEA-6BC7CA151D443B03 [Page Title Here]
etc.

I appreciate if someone could help me understand these directives
better and how analog process them.  I have read the documentation a
number of time, but I'm still missing some things.

Thanks for all the help.

On Tue, Nov 3, 2009 at 11:35 PM, Aengus analo...@eircom.net wrote:
 On 11/3/2009 7:38 PM, Troy Simpson wrote:

 The logs are from an IIS Windows server, but I'm running Analog on a
 RedHat Linux Server.  I had the directive case set to insensitive.
 That was counter intuitive.

 CASE INSENSITIVE

 When I check my setting, the objectID was converted to lowercase.
 Including (+) and excluding (-) the following files:
  All excluded, then
  + /*0847dda0-f261-59bf-faa04eb1ec032b61

 How come this directive works:
 FILEINCLUDE /*?*0847DDA0-F261-59BF-FAA04EB1EC032B61

 But this directive does not work:
 FILEINCLUDE /*0847DDA0-F261-59BF-FAA04EB1EC032B61

 Why do I have to have stars (*) on both sides of the question mark?

 Because 0847DDA0-F261-59BF-FAA04EB1EC032B61 is not a file name, it's an
 argument to index.cfm.

 Aengus
 +
 |  TO UNSUBSCRIBE from this list:
 |    http://lists.meer.net/mailman/listinfo/analog-help
 |
 |  Analog Documentation: http://analog.cx/docs/Readme.html
 |  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
 |  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
 +




-- 
Troy Simpson

+
|  TO UNSUBSCRIBE from this list:
|http://lists.meer.net/mailman/listinfo/analog-help
|
|  Analog Documentation: http://analog.cx/docs/Readme.html
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+


Re: [analog-help] How do I Include pages with specific URL parameters?

2009-11-04 Thread Aengus
Troy Simpson tdsimp...@gmail.com wrote:

 FILEINCLUDE /*?*035E592F-FA2A-267B-5AF64F16D156031F

 REQINCLUDE /*  # This line was important.  But I am not sure why.  The
 Request Report would return 0 request with out this line.

Do you have  REQINCLUDE pages  anywhere in your config file? None of the 
entries captured by your FILEINCLUDE would be recognized as pages by default, 
so they wouldn't show up if you were only including Pages in the Request report.

As I suggested yesterday, adding 
  DIRSUFFIX index.cfm
  PAGEINCLUDE *.cfm
should address this issue, as the .cfm files would be recognized as pages.

 # The following lines are a sample of thelines included via a
 CONFIGFILE directive (232 lines in all).
 REQALIAS REGEXPI:035E592F-FA2A-267B-5AF64F16D156031F [Page Title
 Here]

 I appreciate if someone could help me understand these directives
 better and how analog process them.  I have read the documentation a
 number of time, but I'm still missing some things.

Spend less time reading the documentation, and more time running Analog with 
simple test files, and seeing how changes you make to the configuration change 
the output. It's really the quickest way to understand what's happening - you 
can make a change and run Analog in 10 seconds, rather than waiting a couple of 
hours for an response from the list.

REQALIAS is an output alias - it simply changes what is displayed in the 
Request report. The change only occurs in the output, the actual data itself 
isn't modified. That means that if you REQALIAS two different lines to the same 
thing, you still have 2 entries in the Request Report, whereas if you FILEALIAS 
the same lines to the same thing, you only get one line in the Request Report, 
and the number of requests is the combined number of requests for both lines.

Because your website uses non-human readable URLs for it's pages, REQALIAS is 
a good idea, because you can modify the actual information displayed in the 
Request report to reflect the real page displayed. so you might have

REQALIAS 035E592F-FA2A-267B-5AF64F16D156031F Green Widgets
REQALIAS 03DA02E6-FF9C-FE0B-37856AF28E60357A Blue Widgets
REQALIAS 03DA0008-F3ED-1110-1AB00948167C27F2 Shopping Cart
REQALIAS 03D9FE43-BCE3-8680-163785D70C2B83FF Privacy Notice

(Note that the REGEXPI isn't necessary - you haven't specified a Regular 
expression). Your Request Report would then show the number of requests for 
Blue Widgets, the Shopping Cart, etc, and, if you used the PAGEINCLUDE comamnd 
above, the entries should be clickable (you might need to specify the BASEURL 
too).

Aengus

+
|  TO UNSUBSCRIBE from this list:
|http://lists.meer.net/mailman/listinfo/analog-help
|
|  Analog Documentation: http://analog.cx/docs/Readme.html
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+


Re: [analog-help] How do I Include pages with specific URL parameters?

2009-11-03 Thread Troy Simpson
Thanks for the response.  Please believe me, I have read the manual
several time over.  The practical experience is what is killing me.

So, let me see if I understand this correctly.

The directive of:  FILEALIAS /?objectid=* /*
would translate this:  /?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
to this:  /FEBA5E7B-F1F6-975E-7040A72105801B36

And if I only wanted to report the number of times this page was requested:
 /?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
then I would use the directive:  FILEINCLUDE
/FEBA5E7B-F1F6-975E-7040A72105801B36

Am I on track so far?

Thanks, Troy

On Tue, Nov 3, 2009 at 5:21 PM, Aengus analo...@eircom.net wrote:
 Troy Simpson tdsimp...@gmail.com wrote:
 I am using a content management system (called farcry) to manage and
 display web pages to the public.  The URL includes an objectID
 parameter for each page.  The URL for a page might look something like
 this:

 http://www.domain.com/index.cfm?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
 OR
 http://www.domain.com/?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36

 I want to see how many time a URL with a specific objectID has been
 views.  How do I do that in the analog config file?

 The best that I can come up with is:
 FILEINCLUDE objectid=FEBA5E7B-F1F6-975E-7040A72105801B36

 But that appears to not work.  Am I doing something wrong?

 Because the objectID occurs after the ?, it's an argument, not a file name.
 http://analog.cx/docs/args.html

 You could alias the argument into a filename - something like this:

 FILEALIAS /?objectid=* /*
 FILEALIAS /index.cfm?objectid=* /*

 Aengus

 +
 |  TO UNSUBSCRIBE from this list:
 |    http://lists.meer.net/mailman/listinfo/analog-help
 |
 |  Analog Documentation: http://analog.cx/docs/Readme.html
 |  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
 |  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
 +




-- 
Troy Simpson

+
|  TO UNSUBSCRIBE from this list:
|http://lists.meer.net/mailman/listinfo/analog-help
|
|  Analog Documentation: http://analog.cx/docs/Readme.html
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+


Re: [analog-help] How do I Include pages with specific URL parameters?

2009-11-03 Thread Troy Simpson
The logs are from an IIS Windows server, but I'm running Analog on a
RedHat Linux Server.  I had the directive case set to insensitive.
That was counter intuitive.

CASE INSENSITIVE

When I check my setting, the objectID was converted to lowercase.
Including (+) and excluding (-) the following files:
  All excluded, then
  + /*0847dda0-f261-59bf-faa04eb1ec032b61

How come this directive works:
FILEINCLUDE /*?*0847DDA0-F261-59BF-FAA04EB1EC032B61

But this directive does not work:
FILEINCLUDE /*0847DDA0-F261-59BF-FAA04EB1EC032B61

Why do I have to have stars (*) on both sides of the question mark?

?

On Tue, Nov 3, 2009 at 7:16 PM, Aengus analo...@eircom.net wrote:
 Troy Simpson tdsimp...@gmail.com wrote:
 Thanks for the response.  Please believe me, I have read the manual
 several time over.  The practical experience is what is killing me.

 So, let me see if I understand this correctly.

 The directive of:  FILEALIAS /?objectid=* /*
 would translate this:  /?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
 to this:  /FEBA5E7B-F1F6-975E-7040A72105801B36

 And if I only wanted to report the number of times this page was
 requested: /?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
 then I would use the directive:  FILEINCLUDE
 /FEBA5E7B-F1F6-975E-7040A72105801B36

 Am I on track so far?

 I was going to say yes, but I decided to test it first, and I came across 
 something that surprised me.

 By default, Analog assumes that logs on a Windows system are case 
 insensitive, and logs on a unix system are case sensitive. It handles the 
 case insensitive situation by lowercasing everything.

 BUT!!!

 Items are only aliased once. So when you use FILEALIAS on Windows, you bypass 
 the automatic lowercasing for that request, but the FILEINCLUDE command IS 
 lowercased, so all of a sudden, you have a mismatch between 
 /FEBA5E7B-F1F6-975E-7040A72105801B36 and /feba5e7b-f1f6-975e-7040a72105801b36

 In other words, if you're on Windows, you need to add CASE SENSITIVE to the 
 analog.cfg file too, if you use the FILEALIAS technique.

 On the other hand, if you just use
 FILEINCLUDE /*?*FEBA5E7B-F1F6-975E-7040A72105801B36

 then case isn't an isue, but you will probably also want
 REQFLOOR 1r
 REQARGFLOOR 1r

 if you're doing your tests with one-line logfiles, and
 DIRSUFFIX index.cfm
 PAGEINCLUDE *.cfm

 might also be useful.

 Aengus

 +
 |  TO UNSUBSCRIBE from this list:
 |    http://lists.meer.net/mailman/listinfo/analog-help
 |
 |  Analog Documentation: http://analog.cx/docs/Readme.html
 |  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
 |  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
 +




-- 
Troy Simpson

+
|  TO UNSUBSCRIBE from this list:
|http://lists.meer.net/mailman/listinfo/analog-help
|
|  Analog Documentation: http://analog.cx/docs/Readme.html
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+


Re: [analog-help] How do I Include pages with specific URL parameters?

2009-11-03 Thread Sean at IMAGINET at home

Troy Simpson wrote:

I am using a content management system (called farcry) to manage and
display web pages to the public.  The URL includes an objectID
parameter for each page.  The URL for a page might look something like
this:
http://www.domain.com/index.cfm?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
OR
http://www.domain.com/?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
I want to see how many time a URL with a specific objectID has been
views.  How do I do that in the analog config file?
The best that I can come up with is:
FILEINCLUDE objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
But that appears to not work.  Am I doing something wrong?



Try looking at the documentation about ARGSINCLUDE and look within the 
Request report for the figures being subitems of requests for the 
associated files.


Hope this helps,

-Sean


+
|  TO UNSUBSCRIBE from this list:
|http://lists.meer.net/mailman/listinfo/analog-help
|
|  Analog Documentation: http://analog.cx/docs/Readme.html
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+


Re: [analog-help] How do I Include pages with specific URL parameters?

2009-11-03 Thread Aengus
Troy Simpson tdsimp...@gmail.com wrote:
 I am using a content management system (called farcry) to manage and
 display web pages to the public.  The URL includes an objectID
 parameter for each page.  The URL for a page might look something like
 this:
 
 http://www.domain.com/index.cfm?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
 OR
 http://www.domain.com/?objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
 
 I want to see how many time a URL with a specific objectID has been
 views.  How do I do that in the analog config file?
 
 The best that I can come up with is:
 FILEINCLUDE objectid=FEBA5E7B-F1F6-975E-7040A72105801B36
 
 But that appears to not work.  Am I doing something wrong?

Because the objectID occurs after the ?, it's an argument, not a file name.
http://analog.cx/docs/args.html

You could alias the argument into a filename - something like this:

FILEALIAS /?objectid=* /*
FILEALIAS /index.cfm?objectid=* /*

Aengus

+
|  TO UNSUBSCRIBE from this list:
|http://lists.meer.net/mailman/listinfo/analog-help
|
|  Analog Documentation: http://analog.cx/docs/Readme.html
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+