Splunk Enterprise Security

Infoblox Sourcetype Branch Failures

panovattack
Communicator

We are taking in infoblox logs via syslog and are getting inconsistent results. We have a clustered environment. The infoblox app is installed on a search head and the infoblox data is coming in via syslog on an indexer. On the indexer, the sourcetype is manually set to infoblox:file. The last several days, the branch to infoblox:dhcp and infoblox:dns worked perfectly. Over the last couple days we are now only seeing infoblox:file, as if the sourcetype branches are no longer working. On the search head, we've verified the sourcetypes and the transforms. I can't seem to figure out why this is occurring. Do we need to install the infblox app on the indexer as well? This breaks Splunk Common Information Model (CIM) compliance and by extension Splunk Enterprise Security. Any advice on troubleshooting?

Splunk Add-on for Infoblox Splunk_TA_infoblox 1.0.2

0 Karma
1 Solution

panovattack
Communicator

Resolved by pushing application to indexer.

View solution in original post

0 Karma

panovattack
Communicator

Resolved by pushing application to indexer.

0 Karma

aaraneta_splunk
Splunk Employee
Splunk Employee

Which Infoblox add-on are you using? The TA-infoblox or the Splunk Add-on for Infoblox? I just want to make sure your post is tagged correctly.

0 Karma

panovattack
Communicator

Good catch. Fixed.

0 Karma
Get Updates on the Splunk Community!

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...