Knowledge Management

Feeding data into a data model

bseppanen1
Explorer

I'm working with a standalone splunk 8.1.3 instance with the Splunk CIM 4.20.2.      I have several accelerated data models that are populating data properly.    I have a couple of data sources,specifically an ISC DHCP server logging to a custom UDP port, and a Palo Alto firewall which is logging to its own index, that I'm not finding the data within the data model.   pan:traffic from the palo alto index should constitute network session data, and the ISC DHCP data should likewise.     Is there a way to find out why that data isn't being categorized in that manner?      Is there some way I can get that data in there properly?

 

Thanks,

 

Labels (1)
0 Karma

bseppanen1
Explorer

So i did discover that there is a splunk add on specific to ISC DHCP and I did install that.    That add on doesn't seem to be CIM 4 compliant, so it appears I would have to do that lifting myself and worry that I will implement an Un-Common information model by doing so.     Thanks for your response.

 

It turns out that ISC DHCP Plugin does Support CIM definitions, so I just had to redefine the sourcetype for that to happen properly.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

The key to getting data into a datamodel is to make sure the incoming data uses CIM fields.  Installing the CIM app isn't enough.  You may have to add EVALs or FIELDALIASes to props.conf for the appropriate sourcetypes.

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...