Falcon LogScale 1.70.0 LTS (2023-01-16)
Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Config. Changes? |
---|---|---|---|---|---|---|---|
1.70.0 | LTS | 2023-01-16 | Cloud | 2024-01-31 | No | 1.44.0 | No |
TAR Checksum | Value |
---|---|
MD5 | d9bb7d6cbb0ca0bda19849432c379edf |
SHA1 | b6c06ea11e89db8f31c68b1aa2ad278aad0fe433 |
SHA256 | aaae7b77d39c82f5b6931f7be9da2e03ac7cb68bc7f246529562f3900bf23b02 |
SHA512 | 6370a6f003a2f2ac6f59fdbaa8d7578e2eae7658645bc97cc4ed5f3c75489c914cb09a35e8ca5a6b6203f8a084aac769bc6d9d9b7fd9547fa2cfe9cef6639f40 |
Docker Image | SHA256 Checksum |
---|---|
humio | 9bdd95bb499feb635b2fa10e2ccc8d3738173998679e0b59852b61e9f9072b07 |
humio-core | 8693b1c4fe80d51907f4b706e5f464ed990e365b50099ad8b6a8eb33d370b6cb |
kafka | f22f369876933b93084f34d73014697b6cbae24c3d915e8fb590f2289f4361ce |
zookeeper | b4bb9f58e8a519db4850e395824142fe62fe52f8fcf024de1001fd76481e63c7 |
Download: https://repo.humio.com/repository/maven-releases/com/humio/server/1.70.0/server-1.70.0.tar.gz
Bug fixes and updates.
Deprecation
Items that have been deprecated and may be removed in a future release.
The following environment variables are deprecated as of this release. Their removal will be announced in a future version.
The recommended steps for migrating off of Zookeeper are described in Falcon LogScale 1.70.0 LTS (2023-01-16).
Note
When using Operator and Kubernetes deployments, you must upgrade to 0.17.0 of operator to support migration away from the Zookeeper requirement. See Operator Version 0.17.0.
The query function
holtwinters()
is now deprecated and will be removed along with the release of future version 1.73; therefore, its usage in alerts is not recommended.
Upgrades
Changes that may occur or be required during an upgrade.
Installation and Deployment
We have enabled a new vhost selection method by default. The way hosts select their vhost number when joining the cluster has changed, the new logic is described at Node Identifiers documentation page.
The new logic does not depend on Zookeeper, even for clusters where nodes occasionally lose disk contents, such as Kubernetes. In order to smooth migration for clusters using Zookeeper, the new logic will still interact with Zookeeper to avoid nodes using a mix of new and old vhost code from fighting over the vhost numbers. This is only necessary while migrating.
The recommended steps for migrating off of Zookeeper are as follows:
Deploy the new LogScale version to all nodes.
Remove
ZOOKEEPER_URL_FOR_NODE_UUID
,ZOOKEEPER_URL
,ZOOKEEPER_PREFIX_FOR_NODE_UUID
,ZOOKEEPER_SESSIONTIMEOUT_FOR_NODE_UUID
from the configuration for all nodes.Reboot
Once rebooted, LogScale will no longer need Zookeeper directly, except as an indirect dependency of Kafka. Due to this, the 4 Zookeeper-related variables are deprecated as of this release and will be removed in a future version.
Since vhost numbers now change when a disk is wiped, cluster administrators for clusters using nodes where
USING_EPHEMERAL_DISKS
is set totrue
will need to ensure that the storage and digest partitioning tables are up to date as hosts join and leave the cluster. Updating the tables is handled automatically if using the Logscale Kubernetes operator, but for clusters that do not use this operator, cluster administrators should run scripts periodically to keep the storage and digest tables up to date. This is not a new requirement for ephemeral clusters, but we're providing a reminder here since it may be needed more frequently now.The cluster GraphQL query can provide updated tables (the
suggestedIngestPartitions
andsuggestedStoragePartitions
fields), which can then be applied via the updateIngestPartitionScheme and updateStoragePartitionScheme GraphQL mutations.Should you experience any issue in using this feature, you may opt out by setting
NEW_VHOST_SELECTION_ENABLED=false
. If you do this, please reach out to support with feedback, as we otherwise intend to remove the old vhost selection logic in the coming months.Note
When using Operator and Kubernetes deployments, you must upgrade to 0.17.0 of operator to support migration away from the Zookeeper requirement. See Operator Version 0.17.0.
New features and improvements
Dashboards and Widgets
Added support for export and import of dashboards with query based widgets which use a fixed time window.
Other
Add code to ensure all minisegments for the same target end up located on the same hosts. A change in 1.63 could create a situation where minisegments for the same merge target wound up on different nodes, which the query code currently assumes can't happen. This could cause
Result is partial
responses to user queries.New background task
TagGroupingSuggestionsJob
that reports on flow rate in repositories with many datasources on what it considers slow ones, controlled by configuration of segment sizes and flush intervals. The output in the log can be input to decision on addTag Grouping
to a repository to reduce the number of slow datasources.
Fixed in this release
Security
Update Netty to address CVE-2022-41915.
Automation and Alerts
Fixed a bug where a link in the notification for a failed alert would link to a non-existing page.
Dashboards and Widgets
Fixed three bugs in the
Bar Chart
— where the sorting would be wrong with updating query results in the stacked version, flickering would occur when deselecting all series in the legend, and deselecting renamed series in the legend would not have any effect.Scatter Chart
has been updated:The x-axis would not update correctly with updated query results
The trend line toggle in the style panel was invisible.
Fixed an issue with parameters in dashboards, where the values of a fixed list parameter would not have their order maintained when exporting and importing templates.
Other
Fixed a bug where very long string literals in a regex could cause a query/parser to fail with a stack overflow.
Known Issues
Security
OIDC known issue preventing login:
if you are running LogScale self-hosted, this version will not work in an environment where you are Authenticating with OpenID Connect and you use an HTTP Proxy, but you do not want to call OpenIDConnect through the HTTP Proxy.
Please do not upgrade to this version if this is the case — upgrade to Falcon LogScale 1.63.4 LTS (2023-02-01) and Falcon LogScale 1.70.1 LTS (2023-02-01) instead, where this issue has been fixed.