topic Re: Cisco eNcore eStreamer fields value changed (5.4 -> 6.1) in Getting Data In

Cisco eNcore eStreamer fields value changed (5.4 -> 6.1)

golsida — Tue, 29 Sep 2020 18:56:03 GMT

HI, splunker.

I'm testing two different versions of the estreamer app. (FMC : 5.4, 6.1 / Splunk App : 1629, 3662)
I found two problems with the encore version. (3662) and rec_type=400.

1) src_ip_country is okay (string), but dest_ip_country is number.
2) In the FMC 5.4 and Splunk App 1629, the fw_rule value is displayed as a letter,
but in the FMC 6.1 and Splunk App 3662 version it is displayed as a number.

I wonder if this is a bug or is it intended.
If it is a bug, would you tell me which python source to modify?

Re: Cisco eNcore eStreamer fields value changed (5.4 -> 6.1)

aakwah — Thu, 05 Apr 2018 09:39:47 GMT

You need to check field extraction for the affected sourcetype in props.conf and transforms.conf in the app, or you can send sample from affected log line and the application url on splunkbase to check.

Re: Cisco eNcore eStreamer fields value changed (5.4 -> 6.1)

golsida — Tue, 29 Sep 2020 18:56:28 GMT

@aakwah

I think props.conf and transforms.conf does not matter.
Because, python source code did not define some field.

For example, $SPLUNK_HOME/etc/apps/TA-eStreamer/bin/encore/estreamer/adapters/splunk.py file does not define DESTINATION_IP_COUNTRY, destinationCountry
and $SPLUNK_HOME/etc/apps/TA-eStreamer/bin/encore/estreamer/metadata/view.py file does not define DESTINATION_IP_COUNTRY.

Re: Cisco eNcore eStreamer fields value changed (5.4 -> 6.1)

aakwah — Fri, 06 Apr 2018 07:30:45 GMT

I didn't check the app yet, but for checkpoint app for example the scripted input role is to retrieve the data from the source then field extraction is the responsibility of searchheads via transforms and props.conf.

Once you have the data into the index you can extract the fields the way you like.