Chat now with support
Chat with Support

syslog-ng Store Box 5.2.0 - Release Notes

syslog-ng Store Box 5.2.0

syslog-ng Store Box 5.2.0

Release Notes

October 2018

These release notes provide information about the syslog-ng Store Box release.

Topics:

About this release

Welcome to syslog-ng Store Box. This document describes what is new in the latest version of syslog-ng Store Box (SSB).

Upgrade to the new release

This is a Feature Release, which means that it will be supported for 6 months after the original publication date and for 2 months after a succeeding Feature or LTS Release is published (whichever date is later). Note that only the last of the feature releases is supported - for example, when a new feature release comes out, the last one becomes unsupported.

For a full description on stable and feature releases, open the SSB product page on the Support Portal and navigate to Product Life Cycle & Policies > Product Support Policies > Software Product Support Lifecycle Policy.

Prerequisites and notes

Caution:

SNMP destinations and SQL sources have been removed in the current feature release

Do not upgrade to SSB 5.2.0 if you are currently using and want to continue to use:

  • SNMP destinations
  • SQL sources

These functionalities have been removed from SSB starting with version 5.2.0. Upgrading from 5 LTS and its minor versions would mean that you would have to upgrade to 5.2.0 - to continue to receive support for the product.

Staying on 5 LTS and its minor versions means that you will not have access to the HDFS destination functionality available in SSB starting with version 5.1.0, however, you will continue to get support for 3 years after the original publication date of 5 LTS (December 2017) and for 1 year after the next LTS release is published (whichever date is later).

If you wish to carry on using SNMP destinations or SQL sources, contact zoltan.szasz@oneidentity.com.

Caution:

Pyramid hardware is not supported

SSB 5 LTS is not supported on the following hardware: SSB N1000, SSB N1000d, SSB N5000, SSB N10000.

In case you have SSB deployed on other, newer hardware or you have SSB 4 LTS, those will not be affected in any way. The version policy applies to those. For details, open the SSB product page on the Support Portal and navigate to Product Life Cycle & Policies > Product Support Policies > Software Product Support Lifecycle Policy.

If you wish to take advantage of new features and remain supported beyond the end date of the Extended Support phase, you need to upgrade your hardware. For assistance with your hardware upgrade, contact our Sales Team. For further inquiries, contact our Support Team.

If you do not know the type of your hardware or when it was purchased, complete the following steps:

  1. Login to SSB.

  2. Navigate to Basic Settings > Troubleshooting > System debug, click Collect and save current system state info, and save the file.

  3. Open a ticket at https://support.oneidentity.com/create-service-request.

  4. Attach the file you downloaded from SSB in Step 1.

  5. We will check the type of your hardware and notify you.

How to upgrade

For step-by-step instructions on upgrading to 5.2.0, see Upgrade Guide at the syslog-ng Store Box Documentation page.

New features

  • SSB now uses syslog-ng Premium Edition version 7.0. As a result, the following features have changed:

    • The Pair separator string option has been added to Log > Parsers. You can now define a character or string that separates the key-value pairs from each other.
    • Reliable Log Transfer Protocol (RLTP) has been renamed to Advanced Log Transfer Protocol (ALTP).

    For details on the removed features in connection with this change, see Removed features.

  • From SSB version 5.2.0, SSB now supports SMB 2.1 or later. This change affects your servers and clients that you use for archive, backup and shared logspace purposes. Make sure that they support SMB 2.1 or later. Otherwise these features will not work.
  • On the Log > Sources page, several options have been rearranged to make configuring log sources easier.
  • On the Log > Sources page, the Do not parse option has been added to the Incoming log protocol and message format section. This option completely disables syslog message parsing and stores the complete log in the message part. It is useful if incoming messages do not comply with the syslog format.
  • Because of the change to syslog-ng Premium Edition version 7.0, the Ignore ambiguous program field option has been removed from the Log > Sources page, because syslog-ng PE now handles this both in case of IETF and BSD protocols.
  • On the Basic Settings > Dashboard page, in the syslog-ng module, the following parameter names have changed to better represent their values:

    • destination_stored has been renamed to destination_queued.
    • source_stored has been renamed to source_queued.
  • The Firmware management menu has been removed from the console menu.
  • The Validity information has been removed from Search > Peer Configuration Change.
  • The Peer configuration - Invalid configuration signature element has been removed from the reports.

Removed features

The following is a list of features that have been removed from SSB 5.2.0.

  • Deleted feature 1: SQL source
  • Deleted feature 2: SNMP destination

SSB now uses syslog-ng Premium Edition version 7.0. As a result, the following features have been removed:

  • The SQL source has been removed from Log > Sources. In connection with this, the ssbSqlSourceAlert alert has been removed from Basic Settings > Alerting Monitoring.
  • The SNMP destination has been removed from Log > Destinations.

This means the following:

  • When attempting to upgrade to version 5.2, if you are using SQL source or SNMP destination in your current SSB configuration, the upgrade process will fail. To remedy this issue, delete any SQL source or SNMP destination and retry the upgrade process.
  • When attempting to import a configuration that contains SQL source or SNMP destination to a newly installed SSB, the import process will fail. To remedy this issue, start the machine that you have exported the configuration from, delete any SQL source or SNMP destination, reexport the configuration and then retry the import process.
Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating