Getting Data In

Cisco eStreamer - Some IPS events have incorrect SID

datorres
Explorer

Versions

Splunk Enterprise v7.0.0
Cisco eStreamer eNcore v3.0.0

Problem

I currently have an issue where eStreamer data for IPS events are showing an incorrect value for sid in alert data. The majority of entries do have the correct sid value, but some don't. In the cases where it doesn't, there's a metadata record that shows up in the logs that provides an id field (showing up as sid in IPS events) and then the correct sid field. Here's an example:

Screenshot of Incorrect SID

eStreamer appears to be logging the correct sid everywhere else in our environment; Splunk is the only one that isn't.

Expected Result

Ideally, we would like to have IPS events have the actual sid in that field, not the internal database id.

Anyone happen to have a solution to this? Any help would be greatly appreciated.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...