Getting Data In

ProxySG UTC+2 issue, recommended config

ojay
Path Finder

Hi all,

I'm new to this forum. Would be really happy if you could help me with this.

I am ingesting Bluecode ProxySG logs via syslog as recommended with the log format configuration provided by splunk.

 $(date)T$(x-bluecoat-hour-utc):$(x-bluecoat-minute-utc):$(x-bluecoat-second-utc).000z $(s-computername) bluecoat - splunk_format

https://docs.splunk.com/Documentation/AddOns/released/BlueCoatProxySG/Setup

 

The event time of a proxySG event is always showed with UTC +2 which is causing Splunk to not recognize the time.

Can keep the format configuration and set the ProxySG to local time to avoid the UTC? Will this configuration still be working and simply not just showing +2?

Regards,

O.

Labels (1)
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!

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

How Edge Processor's Durable Queue Works

Edge Processor sits in one of the most consequential places in any Splunk pipeline: between your data sources ...