Getting Data In

Extract Json with different log patterns?

deepthi5
Path Finder

Hi My json logs comes with two different patterns one with timestamp and host added sometimes and one with out these extra fields , when i dont have extra timestamp and host the extractions work better , but for the events with timestamp and host events are not breaking properly 

Type 1 Logs 

   Component: xxxxx
   Data:
   Description: xxxx
   Message: xxxxx

Accessed URL: xxxx
   Originator: xxxx
   Target: xxxx
   appName: xxxxxx
   subTarget: XYZ
   timeStamp: 1668522719915

Type 2 Logs :

Nov 15 15:31:58 ics021013230.ics-eu-1.asml.com {"appName": "XXXXXXX","Component":"XXXXX","timeStamp":"1668522718900","eventId":"2e0525","Description":"XXXX Gateway: YYYYY ","Originator":"xxxxxx","Target":xxxxx","subTarget":"xxxxx"

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

What are the props.conf settings for those two sourcetypes?  They're very different so they should be separate sourcetypes.  Also, the "Type 1" logs are not JSON.

---
If this reply helps you, Karma would be 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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...