Thanks a lot, this is very useful, Our shared graphs are hosted on our sites. So just to make sure: if (putting aside the cache and other issues) 1000 different people/hosts view our graph on page XYZ (which is not our website), analog will show that we've got at least 1000 requests from 1000 individual hosts referred to us by the site "XYZ"?
Regarding cache, I have another question. Is it possible to cache a page and only refresh some of its items (like graphs) without making a new request for page? The reason I ask is because we have several sites and for one of them, analog shows that the number of "requests for pages" per week is three times smaller than the number of "individual hosts served" per week. In other words, an individual host requests less than one page. And this is precisely the site that does not host any graphs – even the graphs which are displayed there come from our other websites. Thus, as far as I know no files from this website are displayed elsewhere and it would seem to me that in order to make any requests from the site, one would have to actually visit it and request at least one page. I know that one possible problem may be the definition of a "page", but analog shows that all major files on the site are .html On Thu, Feb 21, 2008 at 3:16 PM, Aengus <[EMAIL PROTECTED]> wrote: > Natalia Lis <[EMAIL PROTECTED]> wrote: > > Hello, > > I didn't set Analog and I have no background in IT. I'm just trying to > > interpret the results for my company's site. It is a financial website > > with a lot of graphs updated every minute and other sections which are > > also frequently updated. We also share our real-time graphs which are > > very often displayed on third-party websites. > > > > 1.Given that most of our pages contain frequently updated elements, > > what may be the effect of this on the cache issue? Is it reasonable to > > expect that visitors will be less likely to use the cached version and > > our results are less likely to be skewed by this problem? > > It's not a "problem" as such, it's just something to be aware of when > interpreting the data in your log files - some people will be able to "see > your website" without actually making any connection to it, if they use a > caching proxy server and an earlier user has already cached the requested > pages, and other people may appear to be multiple people, if they access your > site through an array of proxy servers. > > In the case of "dynamic" data that is generated "on the fly" every time a > user accesses it, there should be a "no-cache" header that will tell a > caching proxy to always request a "fresh" copy. But if "frequently updated" > means that you generate a new copy every 10 minutes, then it's quite possible > that each copy may get cached somewhere. > > Having said all that, caching doesn't usually have a major impact on the > numbers, and, more importantly, that impact doesn't tend to change much. So > even if there's an X% skew in the numbers, the skew is likely to be X% next > month and the month after that, as long as there haven't been any major > changes in the environment. A different site, though, might have a Y% skew, > because their customer base is different, and their usage pattern is > different. > > > 2.What can be the effect of sharing our graphs on "Individual hosts > > served" category? If people see our graphs on a third-party website, > > those views will count as "requests" in Analog (right?) but will those > > people be included in the "individual hosts served" count or will > > Analog only see the page on which the graphs are displayed? > > There are 2 different issues here - "Individual Hosts Served" means the > number of end users who make a request against your server. "Sharing your > graphs" could mean a number of different things - it could mean that some 3rd > party server copies your graphs and puts it on their site, in which case > you'll never see the requests for those graphs in your log files. Or it could > mean that those sites simpley point to the data on your website, so that the > end user sends the request to your server, and that end user is an > "Individual Host Served". They key difference between such a "3rd party" > visitor, and a direct visitor, is that the "3rd party" visitor will indicate > that "3rd party" in their referrer field. > > For example, if you go to the home page for Analog (http://analog.cx/), > you'll see a button for Sourceforge on the right, below the blue box. The > source for that image is the Sourceforge server. The log files for analog.cx > don't contain any information about whether or not users ever see that > Sourceforge button, but the logfiles for the sourceforge.net server will show > that that image was requested by you, and that you were told to load that > image by the analog.cx page. > > 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 > +------------------------------------------------------------------------ > +------------------------------------------------------------------------ | 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 +------------------------------------------------------------------------
