Business-oriented system usability

Google

ErgoLight
• Usability ...
• Company ...
• Usage Testing ...

Usage Testing:
• User activity ...
• Usage reports ...
• Technology ...
Usage Reports:
• Diagnostics
• Report Spec.
• Procedure ...
• Report example
• Integration
• Web customers
• Free statistics
• To order ...
Procedure:
• Log Requirements
• Delivery
<== Site map Selected Menu path: ErgoLight  >>  Usage Testing  >>  Usage Report >>  Procedure

Site Activity Log File Requirements Specification

 

How do I get the site activity log file(s)?

Ask your site webmaster to get the log files for you

Usually, standard logs of the site visits are automatically generated on the server. It is the administrator of the site host who usually takes care about the generation server log files. Typically, they are automatically extracted to customer log files and stored in a secured directory (such as 'stats') of your site. 
Note: on some installations, the webmaster has to extract the log files manually from the automatically generated server log file.

Using external loggers

What data should be included in the log files?

  • At the minimum, each record of log file should include:
    • Client IP
    • Client-Server URI
    • Time and date
  • It is strongly recommended that the log files will also include the following fields:
    • Server-Client-size
    • Referrer
    • User agent
  • To secure the privacy of your site visitors, the log file must not include any private information that may identify the site visitors. 
  • For best results, ask your webmaster to exclude sessions originated by your site development team (This requirement is important mainly for low traffic sites).

Format of log files

  • The log files should be provided in any of the standard formats. Examples are:
    • Space delimited spreadsheet format (typical to NT servers)
    • Unix server standard format
  • Since the inclusion of most data fields in server log files is optional, it is recommended that the the file format will be specified at the top of the log file(s).

Size of log files

In order to achieve statistically significant results, the log file should be about 10 Mbytes in size (before compression).  You can also send several smaller files, as long as they sum up to about 10M.

Compressing the log file

 To reduce communication load, the log file(s) should be zipped before being sent over for evaluation. Typical compression factor for server log files is about 1:10. This means that the size of the compressed file should be about 1M.

Security warrantee

ErgoLight will save your log files in a secured storage and will not send or sell it to a third party without your explicit permission.

ErgoLight: system design by human factors

 To get a free usage statistics report - http://ergolight-sw.com/CHI/Usage-Testing/Usage-Reports/Free-Report.html

  To order a full usage report - http://ergolight-sw.com/CHI/Usage-Testing/Usage-Reports/Order/To-Order.html

For more information - send your RFP message to: sales.1@ergolight-sw.com: Request for Proposal EMAIL ICON

Did you not find the information you need? Do you want to comment on the website content? Please, send your question or comment to info.1@ergolight-sw.com: Comments on ErgoLight Website Content

Did you experience any problems with this website? obsolete or broken links? inconvenient design? design mistakes? We would appreciate your comments. Please, send them to webmaster@ergolight-sw.com: Comments on ErgoLight Website Design

 Alpha Sites: This particular link is for getting visibility of hosted sites by search engines