All Apps and Add-ons

Splunk Add-on for Cisco WSA: not extracting fields

ashabc
Contributor

Not sure if anyone came across this. I just installed Splunk Add-on for Cisco WSA v 3.1.1.

Ironport WSA Log is indexed as sourcetype cisco:wsa:squid

However, in my search window I am not being able to see any of the fields that is suppose to be extracted by props.conf and transforms.conf of the TA. I am only seeing default fields such as host, source, sourcetype etc,

TA is installed in heavy forwarder, indexer and the search head.

bliss989
Engager

This is what I did to fix the transform. The original did not take into account underscores in the status.
In field transform: kv_for_cisco_wsa_squid

ORG: 19 groups
([0-9.]) *[0-9] ([0-9.]) ([A-Z_])/([0-9]) ([0-9]) ([A-Z]) ([^ ]) "?([^ "])"? ([^/])/([^ ]) ([^ ]) ([^ ]+) <([^,]+),([^,]+),"([0-9]{0,2}|-|\w+)","([^"]+)",[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,"([^"]+)",[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,"([^"]+)",[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^>]+>\s*-\s*"?([^"]+)"?$

FIX: 19 groups
([0-9.]) *[0-9] ([0-9.]) ([A-Z_])/([0-9]) ([0-9]) ([A-Z]\S[A-Z]) ([^ ]) "?([^ "])"? ([^/])/([^ ]) ([^ ]) ([^ ]+) <([^,]+),([^,]+),"([0-9]{0,2}|-|\w+)","([^"]+)",[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,"([^"]+)",[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,"([^"]+)",[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^,]+,[^>]+>\s-\s*"?([0-9.]*).$

Also to get the specific data inbetween the < .... > I replaced: ,[^,]+ with ,([^,]+)

My fix - YMMV - 51 groups
([0-9.]) *[0-9] ([0-9.]) ([A-Z_])/([0-9]) ([0-9]) ([A-Z]\S[A-Z]) ([^ ]) "?([^ "])"? ([^/])/([^ ]) ([^ ]) ([^ ]+) <([^,]+),([^,]+),([^,]+),"([^"]+)",([^,]+),([^,]+),([^,]+),([^,]+),"([^"]+)",([^,]+),([^,]+),([^,]+),"([^"]+)",([^,]+),([^,]+),"([^"]+)","([^"]+)",([^,]+),([^,]+),([^,]+),([^,]+),"([^"]+)","([^"]+)","([^"]+)","([^"]+)","([^"]+)","([^"]+)",([^,]+),([^,]+),([^,]+),"([^"]+)","([^"]+)",([^,]+),"([^"]+)",([^,]+),([^,]+),"([^"]+)","([^"]+)">\s-\s*"?([0-9.]*).$

0 Karma

neelamssantosh
Contributor

Lets give a try,

  1. Hope you are running the search in Verbose mode.
  2. set the fileds extarction to automatic in props.conf, kv_mode=auto

Hope it can help.

0 Karma

ashabc
Contributor

Tired that. It resulted one or two extracted fields and very strange other fields.

I logged a support call with Splunk and been advised its a bug. Reported as ADDON-2774. They provided me a new regex as a work around, but that did not work either.

I rolled back the apps to older version.

0 Karma

o_calmels
Communicator

Hi, from witch app do you send your querry?

0 Karma

ashabc
Contributor

I tried both in search as well as TA for wsa apps (by making it visible). Both same result. It may potentially a bug in the apps.

0 Karma

asifhj
Path Finder

Share the query you are using?

0 Karma

ashabc
Contributor

index=webproxy sourcetype=cisco:wsa:squid

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...