Table of contents

• Upcoming

• Fixes

• Known issues

• New knowledge pack permissions

• Known issue with Elasticsearch 7: “Data too large”

  • Increase available memory for ES

  • (Not recommended) Disable the “real memory circuit breaker”

• Download

• Upgrade

Upcoming

• 2.12 uses Python 3.8

  Python 3.6 is scheduled for End-of-Life on 23rd December 2021. To address this, release 2.12 onwards will use Python 3.8.

• Rebranding to EclecticIQ Intelligence Center in documentation

  Rebranding from EclecticIQ Platform to EclecticIQ Intelligence Center in documentation is in progress. You may still see instances of “EclecticIQ Platform” remaining — please bear with us while we update the documentation.

Fixes

• In distributed environments, feeds may appear to momentarily fail when run

  Fixed an issue where, in certain cases, a feed job may appear to fail, but is actually running.

• In distributed environments, outgoing feeds packing a large amount of data may fail

  Fixed an issue where outgoing feeds may fail due to worker deadlock when attempting to pack a large amount of data in distributed environments.

Known issues

• (Beta) Modern editor can cause UI crash when linking to objects with non-ASCII characters in its title

  You can link to entities or observables in your Reports using both the (Beta) Modern editor and the older editor. However, if the title of that entity or observable contains non-ASCII characters, the UI crashes.

• Elasticsearch 7 encounters “Data too large” errors: See Known issue with Elasticsearch 7: “Data too large”.

• Entity incorrectly warns it is outdated: When viewing an entity, the entity may warn that it is not the latest version when it actually is. This is related to an issue where with attachments that have been depulicated multiple times, causing issues in the final state of the entity.

• When you configure the Intelligence Center databases during a Intelligence Center installation or upgrade, you must specify passwords for the databases.

• Systemd splits log lines exceeding 2048 characters into 2 or more lines.

  As a result, log lines exceeding 2048 characters become invalid JSON, causing Logstash to be unable to parse them correctly.

• When more than 1000 entities are loaded on the graph, you cannot load related entities and observables by selecting Load entities, Load observables, or Load entities by observable from the context menu.

• When creating groups in the graph, it is not possible to merge multiple groups into one.

• If an ingestion process crashes while ingestion is still ongoing, data may not always sync to Elasticsearch.

• Users can leverage rules to access groups that act as data sources, even if those users are not members of the groups they access through rules.

• Running multiple outgoing feed tasks may cause the Intelligence Center to consume a large amount of memory over time, because certain outgoing feeds such as HTTP download must load the data into memory in order to make it available to feed consumers.

New knowledge pack permissions

In 2.11, permissions to install and access knowledge packs have changed from ... configuration-bundles to ... knowledge-packs.

This means that if you’ve previously assigned ... configuration-bundles permissions to users or roles, you have to re-assign the corresponding ... knowledge-packs permissions to allow those users or roles to retain access to knowledge pack features.

Users assigned permissions through the System Admin role are not affected.

The table below lists the changed permissions:

For more specific information on knowledge packs, see the documentation.

Known issue with Elasticsearch 7: “Data too large”

Since release 2.9.0, the Intelligence Center comes bundled with Elasticsearch (ES) 7.9.1. ES 7 adds a new real memory circuit breaker that causes ES nodes to respond with a circuit_breaking_exception error when it detects that memory use has reached 95% of the totally available JVM heap.

Because of this change, you may encounter issues related to available memory where previously at the same workloads, ES would appear to run smoothly.

If your plaform is encountering issues related to Elasticsearch responding with a circuit_breaking_exception error, you can do the following to mitigate:

• Increase available memory for ES

• (Not recommended) Disable the “real memory circuit breaker”

Download

For more information about setting up repositories, refer to the installation documentation for your target operating system.

Upgrade

The following diagram describes the upgrade path you should take depending on the Intelligence Center version you are upgrading from.

For example:

• You can upgrade from version 2.9.1 of the Intelligence Center to 2.10.0 directly,

• To upgrade from 2.4.0 to 2.10.0, you must first upgrade to 2.5.0, then upgrade from 2.5.0 to 2.10.0.

When upgrading from 2.8.x and earlier to 2.9.x and later:

• You must run the pre-upgrade script to allow it to work with Elasticsearch 7.9.1.

  • CentOS

  • RHEL

• You must run the pre-upgrade script on the Intelligence Center version you are upgrading from.

  For example, when upgrading from 2.8.0 to 2.10.1, you must run the pre-upgrade script on the Intelligence Center while it is running version 2.8.0.

From 2.5.0, the upgrades paths have been tested using the EclecticIQ Intelligence Center install script compiled by Rundoc.

The script only supports:

• Single machine installs.

• Instances installed using the Intelligence Center install script.

and does not support Intelligence Center instances installed in distributed environments.