Splunk Search

Untangle Firewall logs not parsed properly into Key/Value pair

hariskhan218
Engager

Hi there,
I have configured Untangle firewall in below mentined fashion.

  1. Configured syslogs port 514 to my splunk instance.
  2. created indexer with _json source type
  3. Below is log format for the firewall

Dec 27 12:46:28 10.10.1.80 Dec 27 12:50:05 localhost node-15: [SyslogManagerImpl] <> INFO uvm[0]: {"protocol":6,"timeStamp":"2017-12-27 12:50:05.603","SClientAddr":"/99.99.99.69","tag":"uvm[0]: ","CServerAddr":"/116.38.203.14","protocolName":"TCP","CClientAddr":"/99.99.99.69","class":"class com.untangle.uvm.node.SessionEvent","hostname":"99.99.99.69","SClientPort":49726,"serverIntf":1,"CServerPort":443,"clientIntf":2,"policyId":1,"sessionId":97828113688465,"SServerPort":443,"SServerAddr":"/216.58.207.14","CClientPort":49726}

Can someone advice on how to properly segregate key values from above logs.
I have tried using json for above source type but no success.

Tags (1)

micahkemp
Champion

This may only be a partial answer, but try:

<your base search>
| rex field=tmp "(?<json>\{.+)" 
| spath input=json

Based on previous answers post.

0 Karma

hariskhan
Explorer

Thanks , that worked.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

@hariskhan, if your problem is resolved, please accept the answer to help future readers.

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

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...