Splunk® Supported Add-ons

Splunk Add-on for Symantec Blue Coat ProxySG and ASG

Acrobat logo Download manual as PDF


Acrobat logo Download topic as PDF

Release notes for the Splunk Add-on for Symantec Blue Coat ProxySG

Version 3.8.1 of the Splunk Add-on for Symantec Blue Coat ProxySG was released on September 12, 2022.

Compatibility

Splunk platform versions 8.1, 8.2, 9.0
CIM
Platforms Platform independent
Vendor Products Bluecoat ProxySG version OS 6.7.5, 7.2.2.1, 7.3.6.1

The field alias functionality is compatible with the current version of this add-on. The current version of this add-on does not support older field alias configurations.

For more information about the field alias configuration change, refer to the Splunk Enterprise Release Notes.

Bug Fixes

Version 3.8.1 of the Splunk Add-on for Symantec Bluecoat ProxySG has the following new features:

  • Fixed the extraction of dest and dest_ip CIM fields


Upgrade

If you are using only one specific version of Blue Coat logs, you can comment out the Report-auto_kv lines for the unused versions in default/props.conf to improve search performance.

Fixed issues

Version 3.8.1 of the Splunk Add-on for Symantec Blue Coat ProxySG has the following fixed issues:

  • Fixed the extraction of dest and dest_ip CIM fields. In v3.8.0 dest field was extracted from the cs_ip and it is corrected to extract from r_ip.


Known issues

Version 3.8.1 of the Splunk Add-on for Symantec Blue Coat ProxySG has the following known issues. If no issues are listed, no issues have yet been reported:


Third-party software attributions

Version 3.8.1 of the Splunk Add-on for Symantec Blue Coat ProxySG does not incorporate any third-party software or libraries.

Last modified on 19 September, 2022
PREVIOUS
Sourcetypes for the Splunk Add-on for Symantec Blue Coat ProxySG
  NEXT
Release history for the Splunk Add-on for Symantec Blue Coat ProxySG

This documentation applies to the following versions of Splunk® Supported Add-ons: released


Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters