Access Log Formats Introduction to Access Logs

9-14 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache ■ x-clf-date ■ x-req-line ■ sc-status ■ bytes ■ csReferer ■ csUser-Agent ■ x-ecid

9.2.1.5 End-User Performance Monitoring Format

This format provides support for the following fields intended for end-user performance monitoring of 10g features: ■ x-req-type ■ x-date-start ■ x-time-start ■ c-ip ■ s-ip ■ x-auth-id ■ csHost ■ cs-method ■ cs-uri ■ x-protocol ■ sc-status ■ bytes ■ cs-bytes ■ x-cache ■ time-taken ■ r-time-taken ■ x-time-delay ■ x-os-timeout ■ x-ecid ■ x-cookieORACLE_SMP_CHRONOS_ST ■ x-cookieORACLE_SMP_CHRONOS_LT ■ x-cookieORACLE_SMP_CHRONOS_GL ■ x-glcookie-set ■ csReferer ■ csUser-Agent ■ x-esi-info ■ x-conn-abrt Logging 9-15 ■ scContent-Type

9.2.2 Access Log Fields

If the default formats are not suitable for your environment, you can create custom log formats by specifying the fields that you require. Table 9–5 describes the supported fields. Fields prefixed with x or r are proprietary to Oracle Web Cache. Table 9–5 Access Log Fields Field Description bytes Content length of the request c-ip IP address of the client cached Integer that specifies cache status. Cache status is reported as the following: ■ 0 specifies a cache miss. Equivalent to M, U, G, and N output of x-cache field. ■ 1 specifies a cache hit of a stale object. Equivalent to S output of x-cache field. ■ 2 specifies a cache hit. Equivalent to H output of x-cache field. csheader_name HTTP request header sent from the client See Also: csheader_name and scheader_name Access Log Fields on page 9-20 cs-bytes Bytes received from the client cs-method Client-to-Oracle Web Cache HTTP request method cs-uri Client-to-Oracle Web Cache URI cs-uri-query Client-to-Oracle Web Cache query portion of URI, omitting the stem cs-uri_stem Client-to-Oracle Web Cache stem portion of URI, omitting the query date Date the transaction completed, in the following format: ddMonyyyy r-ip IP address and port number of origin server. For a cache cluster, this field displays the IP and port number of a peer cache in the cache cluster. The information is displayed in the following format: IP_address:port r-time-taken Time, in seconds including microseconds, that Oracle Web Cache spent communicating with the origin server or peer cache. The time is the duration between the following two points of time: ■ The time immediately before Oracle Web Cache sent the first byte of the request to the origin server or peer cache. ■ The time immediately after receiving the last byte of the response from the origin server or peer cache. This field is particularly helpful in providing time information for end-user performance monitoring. s-ip IP address of Oracle Web Cache computer scheader_name HTTP response header sent from Oracle Web Cache to the client See Also: csheader_name and scheader_name Access Log Fields on page 9-20 9-16 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache sc-status Oracle Web Cache-to-client HTTP status code: ■ 1xx range messages are informational ■ 2xx range messages indicate success ■ 3xx range messages indicate redirection, that is, further action must be taken to complete the request ■ 4xx range messages indicate a client error ■ 5xx range messages indicate a Oracle Web Cache error See Also : http:www.ietf.orgrfcrfc2616.txt for further information about HTTP status codes time Time at which the response from Oracle Web Cache completed. The time is displayed in the following format: hh:mm:ss time-taken Amount of time taken, in seconds including microseconds, for the transaction to complete x-auth-id User name of a basic HTTP authentication request x-cache Cache status. Cache status is reported as the following: ■ H specifies a cache hit ■ S specifies a cache hit of a stale object ■ U specifies a cache update of a stale object ■ G specifies a cache update of an object that was marked for removal but still physically resides in the cache ■ M specifies a cacheable cache miss ■ N specifies a non-cacheable cache miss Table 9–5 Cont. Access Log Fields Field Description Logging 9-17 x-cache-detail Diagnostic information, in the following format: {ESI_processing_type}{cache_request_type} [;max-age=expiration_time[+removal_time];age=object_age] ESI_processing_type is: ■ T specifies that the object is an ESI template ■ F specifies that the object is an ESI fragment ■ Empty specifies that the response does not require ESI processing cache_request_type is: ■ H specifies a cache hit ■ S specifies a cache hit of a stale object ■ U specifies a cache update of a stale object ■ G specifies a cache update of an object that was marked for removal but still physically resides in the cache ■ M specifies a cacheable cache miss ■ N specifies a non-cacheable cache miss max_age specifies the time, in seconds, to expire the object, and optionally, the time, in seconds, to remove the object from the cache after the expiration time. max_age does not appear if the cache_request_type is N. age shows how long, in seconds, the object has been in the cache. age does not appear if the object is non-cacheable. Example: H;max-age=60+30;age=50 ■ H means that this request resulted in cache hit ■ max-age=60+30 means that the object is to expire in 60 seconds from population and to be removed from the cache 30 seconds from the expiration. This provides a total of 90 seconds from population. ■ age=50 means that 50 seconds have passed since population of the cache, meaning there is 10 seconds to expiration and 40 seconds to removal x-cache-key Cache key value, in the following format: cache_key x-clf-date Date that the response from Oracle Web Cache completed, in the following format: ddMonyyyy:hh:mm:ss [+GMT] x-cluster Single character that specifies the status of a cache cluster. The character is reported as the following: ■ T specifies a request to a cache cluster member ■ F specifies a request from a cache cluster member ■ O specifies a request for owned content ■ D specifies a request for on-demand content x-cookiecookie_name Cookie value from client browser request. Table 9–5 Cont. Access Log Fields