Sensor, when used on a server, can collect fields of event data from any valid HTTP request or response header or variable available to it through the server’s API.
To collect such fields of data, you must specify the desired header fields or variables in the txlogd.conf configuration file for Sensor.
Following is the syntax for specifying a request header field to be collected (for example, Host, Accept-Encoding, Keep-Alive, and so on) in txlogd.conf:
The collected data is recorded by Sensor to a field named “cs(RequestHeaderName)” in the .vsl files created by the data workbench server. For example, to collect the specific request header value from the request header “Host,” you would type “LogHeader Host” in txlogd.conf. The data is recorded to the field “cs(Host)” in the event data record.
Sensor can collect fields of data from response headers or API-accessible server variables using SpecialLogField entries that you include in the txlogd.conf file. You can also use “SpecialLogField” entries in addition to or instead of “LogHeader” entries to collect request headers. See Request Headers . The request headers option remains available for backward compatibility.
Following is the syntax for specifying a “SpecialLogField” in txlogd.conf:
SpecialLogField cs(log field) = serverVariable stage
The following table includes descriptions of the components of a “SpecialLogField” entry.
|cs(log field)||The name of the field to which the collected data is recorded in the event data record and the .vsl files created by the data workbench server .|
Any server variable that is available to Sensor through the server’s API
Either vys_log or vys_cookie
Specifying the stage requires that you know which server variables are available for vys_log and vys_cookie.
Example: For the serverVariable response.p3p, you would enter vys_log.
For help configuring Sensor to collect extensible event data record fields, contact Adobe Consulting Services.