All Apps and Add-ons

Splunk for Blue Coat ProxySG: why can't I import using a universal forwarder?

oda
Communicator

http://docs.splunk.com/Documentation/AddOns/released/BlueCoatProxySG/Releasenotes

I am using Splunk Add-on for Blue Coat ProxySG.
I can successfully import using GUI.

However, using universal forwarder does not work.
Does anyone know anything?

I think that the commented out part does not work well.

0 Karma
1 Solution

yutaka1005
Builder

Please add the following settings to props.conf on the forwarder side.

[bluecoat:proxysg:access:file]
INDEXED_EXTRACTIONS = w3c

”INDEXED_EXTRACTIONS” is an item to set at the ”input” stage.
In the case of standalone, if you install add on, you can import the log as it is, but when using forwarder it is necessary to separate the setting values to right phases.

View solution in original post

yutaka1005
Builder

Please add the following settings to props.conf on the forwarder side.

[bluecoat:proxysg:access:file]
INDEXED_EXTRACTIONS = w3c

”INDEXED_EXTRACTIONS” is an item to set at the ”input” stage.
In the case of standalone, if you install add on, you can import the log as it is, but when using forwarder it is necessary to separate the setting values to right phases.

oda
Communicator

Thank you!
Probably it worked!

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...