Getting Data In

Time Conversion of Cisco FTD Logs

teco_akelly
Engager

I have several Cisco FTD devices (managed by Cisco FMC) that are sending syslog messages to splunk. Here is the format....

<164>Sep 19 2021 13:26:27 ftdv-b-int : %FTD-4-313005: No matching connection for ICMP error message: icmp src inside_Mgmt:10.0.20.238 dst inside_Legacy_Server:192.168.0.94 (type 3, code 3) on inside_Mgmt interface. Original IP payload: udp src 192.168.0.94/53 dst 10.0.20.238/12055.

The time is in UTC.... is there a way to convert this time to local when I pull the records in so I can do alerting, etc. on these records?

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Splunk will convert the time zone for you.  You just need to tell it what time zone the event occurs in.  Do that by specifying TZ = UTC in props.conf for the appropriate sourcetype.

I'd be remiss if I missed this opportunity to point out that one should not send syslog directly to a Splunk TCP or UDP port.  Instead, send it to a dedicated syslog server and forward it to Splunk or use Splunk Connect for Syslog.

---
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...