All Apps and Add-ons

Why has onelogin:user taken over parsing all internal logs?

daveywfii
Explorer

I have installed the Onelogin TA and there is a sourcetype parser from that TA that has taken over everything and it is jacking the logs up (onelogin:user). Anybody know why this is happening, and how I can prevent this? 

Labels (1)

letsgopats39
Engager

Run a btool to confirm, but it looks like you have a '[default]' stanza inadvertently assigning the incorrect sourcetype. I'd check for the following in /opt/splunk/etc/apps/splunk_ta_onelogin/local/inputs.conf:

[default]
sourcetype=onelogin:user

 

0 Karma
Get Updates on the Splunk Community!

AppDynamics Summer Webinars

This summer, our mighty AppDynamics team is cooking up some delicious content on YouTube Live to satiate your ...

SOCin’ it to you at Splunk University

Splunk University is expanding its instructor-led learning portfolio with dedicated Security tracks at .conf25 ...

Credit Card Data Protection & PCI Compliance with Splunk Edge Processor

Organizations handling credit card transactions know that PCI DSS compliance is both critical and complex. The ...