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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...