Skip to content

SEAL Elastic Stack 8.17.3

New Features

  • SEAL Elastic Stack has been upgraded to use

    • Elasticsearch 8.17.3

    • Kibana 8.17.3

    • Filebeat 8.17.3

    due to security issues. (ELK-175, ELK-160, 190)

  • The configuration directory and the installation script of SEAL Elastic Stack have been moved to the seal-elasticstack-configuration directory.

    This allows the configuration to be used independently of the local Elastic Stack installation, e. g. to import it into a hosted Elastic Stack System.

    The old configuration directory in the seal-kibana directory is renamed old-configuration.

    (ELK-142)

  • The load-config configuration script uses Node.js. (ELK-143)

  • SEAL Elastic Stack uses it own Node.js version, which is currently 20.16.0 or later. (ELK-157)

  • All Filebeat instances of SEAL Elastic Stack use the filestream input instead of the log input. (ELK-84)

  • The filebeat.log file has been granted 644 access authorization. This allows an administrator who is member of the seal user group to read the log file. (ELK-149)

  • SEAL Elastic Stack 8.x works with DPF 3.x, DPF 4, and PLOSSYS Distribution Engine. (ELK-171)

  • Runtime Fields for the accounting have benn changed to normal fields, which are written by a Pipeline. You have to reindex the accounting data after the update. (ELK-166)

  • The Filebeat configuration has been enhanced by the rotateonstartup: false option. This deactivates the rotation of the log files when Filebeat is started. In updates this option needs to be set manually. (ELK-137)

Bug-Fixes

  • On the DPF admin dashboard, the duration of DPF jobs is displayed in the correct unit. (ELK-169)

  • The DPF configuration has been adjusted that log messages can be sorted into the correct index, despite of missing data fields. (ELK-173)

Known Issues

  • If a job fails, because of errors in the printer language, the resulting error messages are missing in SEAL Elasticsearch. (ELK-155)
Back to top