Knowledge Management

Why a cloned field alias does not work as the original despite having identical permissions and app context?



Trying to map fields from eStreamer data to the ones needed by IDS data model. One of the fields which comes from Sourcefire is "priority" for which there is an existing field alias ( priority -> severity_id), which works fine.

Since CIM needs the field name to be 'severity', I cloned another field alias ( priority -> severity) from the existing and made sure that it has global permission and is part of the TA for sourcefire, same as the field alias for "severity_id".

Still, only severity_id is working but not the one newly created for "severity". Also tried creating the same on indexer but it didn't work. Here is a screenshot showing both the aliases.

alt text

Please advise.


0 Karma

Path Finder

check the props and make sure Field alias is happening only after the Fields extraction

/opt/splunk/bin/splunk cmd btool props list --debug|grep

0 Karma


Hi abhijittikekar,

I'm also experiencing problems with field aliases. Did you ever find a solution to this issue?

0 Karma
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!