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!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...