Stats?

[Anonymous]

Hey PP Gang,

Whilst upgading to PP v1.4, I backed up my database file, and noticed it being rather large. Looking at it, the pixelpost_visitors table is keeping a perminant log of every visitor to hit my site.

What I'm wondering, is there anything that extrapolate the data into something more humanly readable. I'm talking about the likes of Urchin, Webalizer, Http-analyze etc.

Each record contains, date/time, browser, ip, file requested, so it's quite possible to setup something like a program already out there.

If there's nothing out there currently I'll write my own converter so http-analyze and Webalizer can read it (I don't have the time nor skills to write my own stats app)

Thanks,
Wade M

[raminia]

Yeah! we noticed this and it could make the DB act slowly. We need ideas on this. :)

[GeoS]

I've got own stat script for it. AnubisStat - www.anubisdev.com.
I must only speak with main creator of it and maybe we can suply an light version of it for free. It bases on files so it is quite fast.
We will see.

[Anonymous]

raminia: What sort of ideas are you after here???? Features to be placed in it, or ideas on how to code it?

GeoS: I tried checking out your site, but it's not in english so I couldn't get a feel for it.

--Wade M

[GeoS]

@Guest: Here you get demo of this stats:
http://stats.anubisdev.com/

Now it's in PL, DE, EN, FR, ITA & IND. It won't be hard to translate to other langs.

[raminia]

the db in visitor table is getting bug. so bug that if you use this for more than a year it will reduce the speed drastically! we should process the visitors info to new tables and then delete them in a scheduled manner.

[GeoS]

IMHO there should be tables for every month (i.e. called year_month -> 2005_01, 2005_02, 2005_03, etc.) and one global with main stats.

[Anonymous]

GeoS - the Guest was me...never bothered registering an acct here, cheers! :p

Raminia; GeoS's way is the way I'd plan it as well. Have them broken down per month (any more and it gets messy).

Benefits are that it's only ever 1 month to index @ most, which is going to be nowhere near as heavy as 12 months worth.

Keep the results in a master table and whenever an update is run, look @ the master table to find out where it was up to, and then index from there again.

I'm not running a plog (photolog) 4 the visitors I get, but it would be nice to see who/when/where hits are coming from, how google's indexing the site.

GeoS' program is exactly what I'm talking about, it, in my mind would be perfect if it could some how be intergrated into pixelpost.

Looks like this might be going somewhere!!

[blinking8s]

i run my blog in a subdomain, and have full stats displayed in both awstats and urchin

[GeoS]

i run my blog in a subdomain, and have full stats displayed in both awstats and urchin

Not everyone have such possibility :P
I have own script (Anubis), Urchin, AWstat, Webalizer, Analog, ... but other can have non of them or even not any.

[blinking8s]

any why not? installation might be a bit confusing of something like awstats to most...but anyone who actually cares about where they are hosted are going to have these as an option.

[GeoS]

True but if someone have own server on own i-net connection getting something like Urchin can be a small problem for ppl ($$$). Standing up for own use other popular stat system also can be a problem for bigginers (for proff users that isn't but only for proff).

[blinking8s]

not many people are going to have their own server though, shared and virtual private plans are too economical with packages offered today.

anyway, I found http://www.samphp.com/ pretty easy to install...and most host support will install a free stats engine for you if you ask

[steff]

the db in visitor table is getting bug. so bug that if you use this for more than a year it will reduce the speed drastically! we should process the visitors info to new tables and then delete them in a scheduled manner.

I have already a stat service ( http://www.statcounter.com , very nice ;) ) AND i have issues with my provider for MySQL usage because I am limited to 1000 queries/hour.

So is it possible to remove the storage of visitor datas in pixelpost? I prefer my pixelpost blog fast! :)

[Anonymous]

Steff: It'd be REALLY simple to remove that, it's 1 line of code. IF you really want to do it I'll get you the line to comment out (or remove). [1000/hr that's a VERY strict host FYI!]

blinking8s: I don't think you really see what I'm trying to get at here. I have stats for my SERVER, but I just want to see stats for pixelpost. Pixelpost is already logging data specific to it, let's use it.

I don't want to look @ my logs for wi.id.au, which is what my hosting package has stats on. This obviously looks @ everything under that level (which is 5 subdomains), only 1 of these is for photos(pixelpost). The other subdomains all generate traffic as well. When I view my stats, I'm seeing clouded results, I'm seeing 30,000 hits a day to / due to 6 sites in total having / (the 5 subdomains and the domain). I want to JUST look @ photo.wi.id.au.

My hosting company won't let me read the raw logs myself to process them myself, so I can't filter out other domains or just select one (this is common across the hosting industry). As well as having used Urchin/http-analyze and webalizer, none of them has the option to "filter" results [unless I've missed something?].

I also don't want to install a 3rd party solution/picture on my site (like statcounter). Pixelpost is already MAKING all the needed logfiles something just needs to be written to convert them for it's own interface.

If the community isn't even interested in creating a module for this, I will do it offline myself. I can publish the shell code used to convert it into a format, but short of someone else running a linux machine there's no point in me publishing my 'work around'.

Thanks,
Wadem

[GeoS]

It is possible. You must only comment all parts which support this future.

I think that in next versions stat module should be an option for main PP script but added to main distribution.

PS Demo of free to use version of "our" (my friends & mine) stat aplication based on files:
http://anubisdev.com/demo/istat/index.php

To DL avalible here:
http://anubisdev.com/download.php?id=1

PS2 If we are talking only about data which got PixelPost in own DB I can make a panel to view this as nice looking results.

[steff]

Steff: It'd be REALLY simple to remove that, it's 1 line of code. IF you really want to do it I'll get you the line to comment out (or remove). [1000/hr that's a VERY strict host FYI!]



thanks Wadem,
yes please show me what should I remove! :)
I am just interested to show the total number of visitors: will I loose this?
I must admit I like referrers: am I gonna loose those on Pixelpost referrer page?

BTW I just ran out of queries, and upgraded to 10000 queries/hour, damn!

[Anonymous]

Steff,

For the visitor stats to work it must always put something in the DB. It's either the stats for visitors, or no DB access...

(each time someone loads your page there's at least 4 SQL queries being run, to populate everything).

GeoS, I REALLY hate to be rude, but I've had a hard time understanding your english below :(

Thanks,
Wadem

[blinking8s]

wadem - i did understand you, from my experience with most server setups (non-windows) subdomain stats are generally seperate from the main domains stats...

what specific information do you wish to see provided from a stats addition to pixelpost? i can see it being a solid add-on feature, but not built in...we need to clean up the current log system as it is...

[Wadem]

blinking8s: Yes, apache by default keeps seperate logs for different subdomains. I don't run PP on a server I control, and on my server the logs are merged. I have it on a subdomain of a commerical server (which runs ensim).

Ensim doesn't keep the logs seperate, it merges them. I know cpanel keeps the logs seperated and eventually I'll move hosts to one that has seperate subdomain logging.

The thing is, regardless of a hostside feature, I think it would be a nice feature. What about those who run it on a main domain and want to only see refferlogs/country access/time/date/browser/robots for PP, not their whole domain. All stats programs show the above information for the WHOLE domain, the only information that's broken down per directory is the hits/entry/exit.

It's obviously not a high priority feature as it's not client facing feature/function and it doesn't really make the user's side easier either. It would be a nice feature tho.

Until I change hosts, and until you get this running server side, I'm going to write a script that uses the DB entries and processes it into a ELF so I can import it into webstats.

Thanks for your time/s!
--Wadem

[doffer]

It might be an idea to count all the visitors from the 1st tho the 31st every mont and record that as something like an line in a new table for monthly visitors...

That way you would only have the visitors from the last month with a lot of info, but that's enough for most users...

[Fellow Eskimo]

Well...the thing that I have had problems with (and I know this is probably stupid...) Ive been putting them in the index.php page. And...it counts everytime someone goes to a new picture. I just want to see where they come from once they get to the MAIN page. I dont care about people going though the archives. Is there another place to stick a counter? If fixing to put the PHP i-stats on my host.