Statistic with webalizer

Next topic

Author	Message
Milan Gabor	Monday 17 February 2003 11:28:00 am I am playing little bit with lates release and I tried to run webalizer on apache logs, but there is problem, since everything is rewrited to index.php, so I cannot see how often is some section visited. Is there any way to get detailed statistics? I also miss functionality of URL translator. Is in ezp 3 also possible to map let say /news to /content/view/full/XXX ? MIlan
Brendan Pike	Wednesday 05 March 2003 6:10:13 pm > I am playing little bit with lates release and I tried to > run webalizer on apache logs, but there is problem, since > everything is rewrited to index.php, so I cannot see how > often is some section visited. > Is there any way to get detailed statistics? How did you go with this, did you end up finding answers? It is of interest to me also. www.dbinformatics.com.au We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.

Author

Message

Monday 17 February 2003 11:28:00 am

I am playing little bit with lates release and I tried to run webalizer on apache logs, but there is problem, since everything is rewrited to index.php, so I cannot see how often is some section visited.
Is there any way to get detailed statistics?

I also miss functionality of URL translator.
Is in ezp 3 also possible to map let say /news to /content/view/full/XXX ?

MIlan

Brendan Pike

Wednesday 05 March 2003 6:10:13 pm

> I am playing little bit with lates release and I tried to
> run webalizer on apache logs, but there is problem, since
> everything is rewrited to index.php, so I cannot see how
> often is some section visited.
> Is there any way to get detailed statistics?

How did you go with this, did you end up finding answers? It is of interest to me also.

www.dbinformatics.com.au

We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.

eZ debug

Timing:	Jan 30 2025 21:10:27
Script start
Timing:	Jan 30 2025 21:10:27
Module start 'layout'
Timing:	Jan 30 2025 21:10:27
Module start 'content'
Timing:	Jan 30 2025 21:10:27
Module end 'content'
Timing:	Jan 30 2025 21:10:27
Script end

Main resources:

Total runtime	0.0227 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0043	588.1563	151.2109
Module start 'layout'	0.0043	0.0030	739.3672	220.6875
Module start 'content'	0.0073	0.0139	960.0547	997.7109
Module end 'content'	0.0212	0.0015	1,957.7656	29.9922
Script end	0.0227		1,987.7578

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	10.7781	14	0.0002
Check MTime	0.0010	4.5872	14	0.0001
Mysql Total
Database connection	0.0006	2.7733	1	0.0006
Mysqli_queries	0.0018	7.8892	3	0.0006
Looping result	0.0000	0.0357	1	0.0000
Template Total	0.0011	4.7	1	0.0011
Template load	0.0008	3.4911	1	0.0008
Template processing	0.0003	1.1423	1	0.0003
Override
Cache load	0.0006	2.4686	1	0.0006
General
dbfile	0.0025	11.1680	8	0.0003
String conversion	0.0000	0.0273	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs