The Learning Log node will send the request's informations in the learning log database. This database can then be used to train sitemaps.
As each learned request will be store in the database, it is recommended to learn only portion of the traffic.
The maximum number stored logs can be set in the Global Settings section (Databases retention).
Learning log and performances
Beware, the activation of the access log to database is very consuming in terms of CPU, memory and disk space. Our recommendation is to use a dedicated Management appliance for the cluster configuration and log storage. Managed appliances will only handle traffic.
Display name: the name of the node
Tag: a custom text that is added to the learning log and used to filter them before training a sitemap.
Tag's Length: the maximum length of the tag.
Before sending the log, all non alphanumeric character will be removed, the tag will be lowercased and trunked to the maximum length.
appliance.uid: the appliance handling the request
http.request.hostname: the hostname used in the request
http.request.ip-src: the IP Address of the client
http.request.method: the HTTP method of the request
http.request.path: the HTTP path of the request
rproxy.uid: the reverse pxory handling the request
tunnel.uid: the tunnal handling the request
When the following attributes are available, the node use them. If not, empty values are used.
http.response.status: the HTTP status code of the response (if available)