Log Decoder Service Configuration ParametersLog Decoder Service Configuration Parameters
This topic lists and describes the available configuration parameters for Log Decoder configuration settings.
|Log Decoder Setting Field||Description|
/database/config refer to "Database Configuration Nodes" in the NetWitness Platform Core Database Tuning Guide.
/decoder/config refer to Decoder Configuration Parameters.
/index/config refer to "Index Configuration Nodes" in the NetWitness Platform Core Database Tuning Guide.
/logs/config refer to Core Service Logging Configuration Parameters.
/rest/config refer to REST Interface Configuration Parameters.
/sdk/config refer to "SDK Configuration Nodes" in the NetWitness Platform Core Database Tuning Guideand NetWitness Platform Core Service system.roles Modes.
/sys/config refer to Core Service System Configuration Parameters.
Log Tokenizer Configuration Settings
The Log Decoder has a set of configuration items that control how the automatic log tokenizer creates meta items from unparsed logs. The log tokenizer is implemented as a set of built-in parsers that each scan for a subset of recognizable tokens. The functionality of each of these native parsers is shown in the table below. These word items form a full-text index when they are fed to the indexing engine on the Concentrator and Archiver. By manipulating the parsers.disabled configuration entry, you can control which Log Tokenizers are enabled.
|Parser Name||Description||Configuration Parameters|
|Log Tokens||Scans for runs of consecutive characters to produce 'word' meta items.||token.device.types, token.char.classes, token.max.length, token.min.length, token.unicode|
|IPSCAN||Scans for text that appears to be an IPv4 address to produce ip.addr meta items.||token.device.types|
|IPV6SCAN||Scans for text that appears to be an IPv6 address to produce ipv6 meta items.||token.device.types|
|URLSCAN||Scans for text that appears to be a URL to produce alias.host, filename, username, and password meta items.||token.device.types|
|DOMAINSCAN||Scans for text that appears to be a domain name to produce alias.host, tld, cctld, and sld meta items.||token.device.types|
|EMAILSCAN||Scans for text that appears to be an email address to produce email and username meta items.||token.device.types|
|SYSLOGTIMESTAMPSCAN||Scans for text that appears to be syslog-format timestamps. Syslog is missing the year and time zone. When such text is located, it is normalized into UTC time to create event.time meta items.||token.device.types|
|INTERNETTIMESTAMPSCAN||Scans for text that appears to be RFC 3339-format timestamps to create event.time meta items.||token.device.types|
Log Tokenizer Configuration Parameters.
|Log Decoder Parser Setting Field||Description|
The set of device types that will be scanned for raw text tokens. By default, this is set to unknown, which means only logs that were not parsed will be scanned for raw text. You can add additional log types here to enrich parsed logs with text token information.
If this field is empty, then log tokenization is disabled.
This field controls the type of tokens that are generated. It can be any combination of the values alpha, digit, space, and punct. The default value is alpha.
This field puts a limit on the length of the tokens. The default value is 5 characters. The maximum length setting allows the Log Decoder to limit the space needed to store the word metadata.
This is the minimum length of a searchable text token. The minimum token length will correspond to the minimum number of characters a user may type into the search box in order to locate results. The recommended value is the default, 3.
This boolean setting controls whether unicode classification rules are applied when classifying characters according to the token.char.classes setting.