All Apps and Add-ons

App for McAfee Web Gateway: Why are events logged with timestamps as 5 years old?

MEfimov
Explorer

Hi,

The App for McAfee Web Gateway is installed and configured by attached manual, but all events have timestamp -5 years. Instead 19/01/2016 logged 19/01/2011. MWG time was set up correctly. What I've missed?

0 Karma
1 Solution

MEfimov
Explorer

Thanks, already found this. I've added TIME_FORMAT = %b %d %H:%M:%S to the props.conf under [MWGaccess3] and now all seems to be ok.

0 Karma

Richfez
SplunkTrust
SplunkTrust

Can you paste one raw event and what time it was timestamped at? I don't know how that data gets in, but it would be even better if you include that actual event as generated before Splunk saw it (either from syslog or from the web gateway itself?).

0 Karma

MEfimov
Explorer

Thanks for reply. Raw message (looked in tcpdump) contains timestamp without year. For example:

Jan 20 10:08:21 proxy mwg: status=....

I have commented line
#$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
in rsyslog.conf and I see that /var/log/messages contains full timestamp, but events are sent still in short format

0 Karma
Get Updates on the Splunk Community!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...