This section describes the format of the CSV file created by the dbprt command as a means of exporting data from the SQC Usage database.
This section explains the format of the comma separated value (CSV) file that is created after execution of the dbprt command.
The CSV file is a text file. The text character code depends on the platform used.
[Windows]
Character code |
|---|
ASCII |
UNIX]
Character code |
|---|
ASCII |
Data is separated with a comma (,) and output to the file. The file consists of the following lines:
Title line Data line Data line : : Data line |
The following table lists explanations of each line:
Line | Explanation | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Title | The field name (item name) of each field is output to only the first line as the title line. Each field is delimited by a comma (,). | ||||||||||||||
Data | On the second and subsequent lines, multiple data lines are output as results of editing. On each data line, one piece of data edited each hour is output. Data is displayed in ascending order of date/time (chronological order). Each field is separated by a comma (,). The date field and time field are placed in this order and then fields depending on the data type are placed. The format of the date field is as follows:
The format of the time field is as follows:
| ||||||||||||||
Format for each data type
The following table lists details of the title line and data line for each data type. Although the format description in this table extends over multiple lines, the actual output is one line.
Data type | File output format | |
|---|---|---|
session (session information) | Title line (1st line) | date,hour,c-host,c-ip,authuser,r-host,r-ip,url,entry-request,exit-request,session,c-acsid |
Data line (2nd and subsequent lines) | yyyy/mm/dd,h,"c-host","c-ip","authuser","r-host","r-ip","url",entry-request,exit-request,session,"c-acsid" | |
request (request information) | Title line (1st line) | date,hour,c-host,c-ip,authuser,r-host,r-ip,url,s-traffic,e-traffic,e-request,c-hit,s-hit,r-hit,c-acsid |
Data line (2nd and subsequent lines) | yyyy/mm/dd,h,"c-host","c-ip","authuser","r-host","r-ip","url",s-traffic,e-traffic,e-request,c-hit,s-hit,r-hit,"c-acsid" Remarks: The total request count is the sum of e-request, c-hit, s-hit, and r-hit. | |
error (error information) | Title line (1st line) | date,hour,c-host,c-ip,authuser,r-host,r-ip,url,s-error-code,r-error-code,e-request,c-acsid |
Data line (2nd and subsequent lines) | yyyy/mm/dd,h,"c-host","c-ip","authuser","r-host","r-ip","url","s-error-code","r-error-code",error-num,"c-acsid" | |
agent (agent information) | Title line (1st line) | date,hour,c-host,c-ip,url,agent,session |
Data line (2nd and subsequent lines) | yyyy/mm/dd,h,"c-host","c-ip","url","agent",session | |
link (referrer information) | Title line (1st line) | date,hour,l-host,l-ip,l-url,r-host,r-ip,r-url,url,session |
Data line (2nd and subsequent lines) | yyyy/mm/dd,h,"l-host","l-ip","l-url","r-host","r-ip","r-url","url",session | |
response (response information) | Title line (1st line) | date,hour,c-host,c-ip,url,avr-response,max-response,min-response |
Data line (2nd and subsequent lines) | yyyy/mm/dd,h,"c-host","c-ip","url",avr-response,max-response,min-response | |
Explanation of fields on the 2nd and subsequent lines for each data type
Field | Meaning |
|---|---|
yyyy/mm/dd | Date field |
h | Time field |
"agent" | Agent name |
"authuser" | Authentication user name. If no data is available, "-" is output. |
"c-host" | Client host name. If no data is available, "-" is output. |
"c-ip" | Client IP address. If no data is available, "-" is output. |
"c-acsid" | Access ID set by Cookie |
"url" | URL of the Web page |
"l-host" | Referrer host name |
"l-ip" | Referrer IP address |
"l-url" | Referrer URL |
"r-host" | Remote host name |
"r-ip" | Remote IP address |
"r-url" | Remote URL |
"s-error-code" | Code for error that occurred on the server. If no data is available, "-" is output. |
"r-error-code" | Code for error that occurred on the remote server. If no data is available, "-" is output. |
session | Session count |
c-hit | Hit count on the client |
s-hit | Hit count on the server |
r-hit | Hit count on the remote server |
entry-request | Entry request count |
exit-request | Exit request count |
s-traffic | Successful request traffic |
e-request | Failed request count |
e-traffic | Failed request traffic |
error-num | Error count |
avr-response | Average response time (in milliseconds) |
max-response | Maximum response time (in milliseconds) |
min-response | Minimum response time (in milliseconds) |
This section provides an example of capacity estimation under the conditions shown below. Refer to this example when you estimate the capacity by applying each CSV-output data type and periods.
Conditions
Data type | Visit information |
|---|---|
Size per line | About 150 bytes (depending on the length of the client name and URL) |
Access count | About 10,000/day |
Approximate maximum size per day
About 150 bytes * about 10,000 = about 1.5 MB (/day)
Actually, the same visitor (client) may often visit the same URL more than once within the same one hour. In such cases, the data of this kind is summarized on one line, and therefore actual size becomes smaller than the above size if the total access count is the same.
