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.7.0 of the Splunk Add-on for Symantec Blue Coat ProxySG was released on October 20, 2019.

Compatibility

Splunk platform versions 8.0.0, 7.3.x, 7.2.x
CIM 4.17
Platforms Platform independent
Vendor Products Bluecoat ProxySG version OS 5.3.3, 6.5.x, 6.6.3.2, 6.6.4.2, 6.7.5, 7.2.2.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.

New Features

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

  • Support for Bluecoat ProxySG version 6.7.5 and 7.2.2.1 has been added to sourcetypes bluecoat:proxysg:access:file and bluecoat:proxysg:access:kv.

Additional Notes

Please note the following changes in this release:

  • bcereportermain_v1 configurations for the bluecoat:proxysg:syslog sourcetype is supported only for versions 5.3.3, 6.5.x, 6.6.3.2, 6.6.4.2.
  • bluecoat:proxysg:access:kv is recommended for collecting syslog data going forward.
  • The eventtype bluecoat_traffic_monitor is removed from this release.
  • The Web CIM field category is now a single-value field instead of a multi-value. The multi-value is now captured in vendor_categories.
  • inputs.conf in the default directory is no longer shipped in the add-on,
  • Support for the following fields have been removed:
    • cs_Cookie
    • cs_host
    • c_port
    • s_port
    • cs_ip
    • cs_protocol
    • c_pkts_received
    • s_session_id

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.

Unlike previous versions, versions 3.5.0 and above of the Splunk Add-on for Symantec Blue Coat ProxySG do not support Blue Coat version 5.3.3 logs by default. If you want to ingest version 5.3.3 logs, complete these steps:

  1. Open or create a local/props.conf file.
  2. Open default/props.conf.
  3. Copy the #REPORT-auto_kv_for_bluecoat_v5 = auto_kv_for_bluecoat_v5_3_3 line in the bluecoat:proxysg:access:syslog stanza in default/props.conf.
  4. Paste the #REPORT-auto_kv_for_bluecoat_v5 = auto_kv_for_bluecoat_v5_3_3 line in the bluecoat:proxysg:access:syslog stanza into local/props.conf.
  5. Uncomment the #REPORT-auto_kv_for_bluecoat_v5 = auto_kv_for_bluecoat_v5_3_3 line in local/props.conf.

Fixed issues

Version 3.7.0 of the Splunk Add-on for Symantec Blue Coat ProxySG has the following fixed issues. If no issues follow, no issues have yet been reported:


Known issues

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


Third-party software attributions

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

Last modified on 11 March, 2021
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