"Meta not available on device" is displayed in RSA NetWitness investigations.
When adding a custom log meta key to an RSA NetWitness device using the table-map.xml file, the error "Meta not available on device" is displayed in Investigation.
After editing the table-map.xml file and changing the value from "transient" to "none" and adding the key to the index-logdecoder.xml file, "Meta not available on device" is displayed for the custom value in Investigation.
At times, the standard table-map.xml and index-<service>.xml files have required updating, and those changes are introduced in the upgrade or patching process. When these new templates are introduced, new xml files are deployed, which overwrite existing xml files, thus taking the customized changes with them.
This usability issue prompted the introduction of a different method to add custom keys to the configuration. As of RSA Security Analytics 10.3, custom changes must be introduced in new custom xml files to be recognized.
To toggle data types from memory resident to disk, the value for "flags" must be toggled from "transient" to "none" in a new file called table-map-custom.xml. All index-<service>.xml changes must also be recorded in their own file, index-<service>-custom.xml. The table-map.xmland index-<service>.xmlfiles should no longer be edited. Use only the customxmlmodel to make changes.
The adoption of this model introduces two distinct advantages: a) the customizations will no longer be overwritten during software upgrades, and 2) easing administration to manage customizations to xml files, as delta change management for customizations is no longer necessary.
Before beginning: All commands are executed as root from the command line of each device as noted to the specific device. All installations must execute steps for the A) Log Decoder and B) Concentrator, and sites with an optional broker must also execute C) Broker steps. Process restarts of the log decoder, concentrator and broker are required to recognize these changes. When in production, schedule accordingly.
The below steps exemplify the process using "Severity" as the custom key example.
I. Log decoder(s):
Execute these steps on all log decoders:
On the log decoder, data that is marked as "Transient" is memory resident and not written to disk, data that is set to "None" is parsed and written to disk. In order to write meta, you must set the value to "None".
Issue the following command to enter the appropriate directory:
# cd /etc/netwitness/ng/envision/etc
Locate the key you wish to use in the current table.map.xml file. (vi hint: use the search feature in vi, <esc> / then enter the word "severity" and hit return)
After locating the matching key, which by default is set to "Transient" as shown in the example below, the flag must be set to "None".