Falcon LogScale 1.76.0 Preview (2023-02-07)
Version | Type | Release Date | End of Support | Upgrades From | Data Migration | Config. Changes |
---|---|---|---|---|---|---|
1.76.0 | Preview | 2023-02-07 | 2023-02-27 | 1.44 | No | No |
Bug fixes and updates.
Improvements, new features and functionality
Deprecation
Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.
UI Changes
Event List Interactions are now sorted by name and repository name by default.
Dashboards and Widgets
The
Single Value
widget now supports interactions on both the Search and Dashboard page. See Managing Dashboard Interactions for more details on interactions.It is now possible to set a temporary timezone in dashboards, which will be read from the URL on page load.
For more information, see Time Interval Settings.
Log Collector
LogScale Collector Fleet Management now supports remote configuration of LogScale Collectors. This gives an administrator the option of managing the configuration of LogScale Collector instances in LogScale, instead of managing configuration files directly on the device where Falcon Logscale Collector is installed.
For more information, see LogScale Collector Fleet Management, LogScale Collector Releases.
Functions
Queries containing a
join()
function no longer run truly live when the query is set to Live. Instead, these queries will run repeatedly at intervals determined by the query engine.For more information, see Warnings when Using Live join() Functions, Creating Widgets with Live join() Functions,
join()
, Special Behaviour for Live Joins.
Bug Fixes
Other
Fixed an issue for the ingest API that made it possible to ingest into system repositories.
Prewarning; the following items are due to change in a future release.
Configuration
Starting from 1.78 release, the default value for the
MAX_INGEST_REQUEST_SIZE
configuration will be reduced from1 GB
to32 MB
.This value limits the size of ingest request and rejects oversized requests.
If the request is compressed within HTTP, then this restricts the size after decompressing.