Getting Data In

SC4S parsing issues

Jasem
Explorer

I have set SC4S up using Docker CE and systemd. In env file, I have a HEC endpoint url and a custom UDP port open, here is the error I get for 100% of Cisco FTD logs:

dtparse: Expected:                      '%b %d %H:%M:%S.%f',                     '%b %d %H:%M:%S',                     '%b %d %I:%M:%S %p.%f',                     '%b %d %I:%M:%S %p',                     '%b %d %Y %I:%M:%S %p.%f'                     '%b %d %Y %H:%M:%S.%f',                     '%b %d %Y %H:%M:%S',                 ; Actual: 	60,905

and for Fortiweb logs, I get all logs parsed with no host field extracted. has anyone faced these issues before?
Thanks in advance.

Labels (1)
Tags (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

This suggests discrepancy between sc4s parsing rules and the actual event format. Have you actually compared your events with "standard" events sc4s expects? AFAIR sc4s project site lists specific configurations that need to be applied on the source side so that it produces events compatible with sc4s.

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!

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...

Splunk Brings Proof of Control to Digital Asset Transfers

Digital assets now sit inside the core of financial services. HSBC launched its Tokenized Deposit Service in ...

Manage Ingest Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Ingest Processor pipeline, deploy it to the ...