|
| I've just activated Portal 6's Site Analysis log service, and discovered that the amount of data being captured is much greater than it was under Portal 5.0.x. Unfortunately, much of the raw data is irrelevant to me. Take the following, which is a single
line that logs one of the portlets that loaded on a page (bolded text is info that's actually useful to me):
<b><ip/hostname> - <userID> [22/Mar/2007:17:13:27 -0500]</b> "GET /Portlet/& #91;ObjectIDImpl_'5_46LSVKG10O7F10219HTB
UE30F7'_[1702079236413478084:-1224735118897641344@0_/_PORTLET_ENTITY],_Domain:_& #91;Domain:_rel],_DB_representation:_000
0-C454FE290C009F17800829F6E
5DD00EF]/<b>ZMkup_whatsnew_portlet</b>?PortletPID=& #91;ObjectIDImpl_'5_46LSVKG10O7F10219HTB
UE30F7'_[1702079236413478084:-1224735118897641344@0_/_PORTLET_ENTITY],_Domain:_& #91;Domain:_rel],_DB_representation:_000
0-C454FE290C009F17800829F6E5DD00EF]&PortletMode=View
&PortletState=Normal HTTP/1.1" 200 -1 "<b>http://192.168.2.7/Page/</b>& #91;ObjectIDImpl_'6_46LSVKG100098021IV71
G11GV3'_[- 8899112811439958844:9187416909798312064@
0_/_CONTENT_NODE],_Domain:_& #91;Domain:_rel],_DB_representation:_000
0-C454FE290C0080848008F29F0043807F
]/<b>Test_Page</b>" "<b>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3"</b> "CP=null*;JSESSIONID=0000-yMHZFjxBzP4mKe6k1PU6Ne:-1;LtpaToken=zWjUGUmA6k43VjDd/ UvzZfmv3JldV5UEC+pa9fz9sLI3jE6r7L0wE9VKo
rEcyNwQTzHM0yvqq
kTIaRuYIEsIaMTrllKYozuEVpiDomxB5DQE8gFWF
e8ZhJfYayLz7bgB3LwT6Un6hE61B7Tiig7Yqmgvj
GNFz3DQ22HBgJmeYojDEeK3ebRL9uqZJkTE74DBJ
GJocPMkh3yiBTuZ0oS6PZO0FqHWItmIQ6i+Cqs6a
qSQiPtfY19oC4tFdH6kz/D5jvBE8M/ 0WMvHYqbSifJNu3hXOMZs3Emx8xmW15ZjMSYDNbW
1qSEjbn9v7nJzJ0uV09k8b3AF
iwHkEBDOHBl4cxrjy2KiwC74"
The following loggers are on:
SiteAnalyzerSessionLogger
SiteAnalyzerPortletLogger
SiteAnalyzerErrorLogger
Is there any way to pare down the unwanted info? If not, the log files will balloon in size, fast--one user hitting a single page with six portlets on it increased the log size by 12 kB.
|
|