From: "Jami Ryan" <[EMAIL PROTECTED]> > My problem is I've configured Analog to read cookies as unique > users. While this has worked great in the past, a second cookie > has been added on my site. So now I have two cookie values getting > reported in the user report, but the main problem is the new cookie > value is not a constant so I believe Analog is reporting a lot more > users than what it should because every time this cookie value > changes, I believe I get another user. (My guess is I'm getting > double the correct amount.)
The simplest way to verify that guess is to take 5 or 10 lines from you log file, calculate how many "users" you see manually, and then have anlof report on the lines, and see if it agrees with your count. If you take 10 lines at random from throughout your logfile, and your manual count agrees with Analog, then it's likely to be right for a large sample. > Also, I wanted to make sure I am interpreting the function of > the user exclude command correctly. From what I've read on the > Analog site, I get the impression that using the user exclude > command or any exclude command for that matter, takes all matching > log file lines completely out of the report meaning that these > particular lines are ignored when processing the data. Is my > interpretation correct? This is correct. > And, just in case you were wondering what my log file looks > like in regards to the cookies and how I'm using the user alias > command, here is the code: > > > Possible Cookie Formats: (From my logfiles) > poppedup=yes;+ASPSESSIONIDQGGGQNDG=ILBNHIJBCOIKKLKCLCCGONGM >BEV=63.25.78.222.13445966995796876;+poppedup=yes;+ASPSESSIONIDQGGGQNDG=FM BNHIJBLFGPHJHGCMBBAFCA > ASPSESSIONIDQGGGQNDG=FHBNHIJBJAGPJGGEKDEMIAHJ > ASPSESSIONIDQGGGQNDG=HGBNHIJBCPPGPPOGOBLMAAAK;+poppedup=yes > poppedup=yes > > (Also can be nothing, such as: - ) > > > User Alias Code: (I want to compare only the value of the ASPSESSION > Cookie to distinquish different users) > > USERALIAS *ASPSESSION*=*;* $3 > USERALIAS *ASPSESSION*=* $3 "poppedup=yes" will still show up as a user in that case, so that the sample lines you give produce this User Report: Listing users, sorted alphabetically. no.: reqs: %bytes: user ---: ----: ------: ---- 1: 1: : fhbnhijbjagpjggekdemiahj 2: 1: : fmbnhijblfgphjhgcmbbafca 3: 1: : hgbnhijbcppgppogoblmaaak 4: 1: : ilbnhijbcoikklkclccgongm 5: 1: : poppedup=yes You could use USERREPEXCLUDE "poppedup=yes" to exclude this from the report without excluding the lines involved from the other reports. Aengus +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
