Falcon LogScale 1.87.0 Preview (2023-04-25)
Version | Type | Release Date | End of Support | Upgrades From | JDK Compatibility | Data Migration | Config. Changes |
---|---|---|---|---|---|---|---|
1.87.0 | Preview | 2023-04-25 | 2023-05-24 | 1.44 | 11 | No | No |
Bug fixes and updates.
Improvements, new features and functionality
Dashboards and Widgets
When using the Edit in search view item on a dashboard widget, the values set in parameters in the query are also carried over into the search view.
When Setting Up a Dashboard Interaction, the
{{ startTime }}
and{{ endTime }}
special variables now work differently, depending on whether the query, widget or dashboard is running in Live mode or not. They now work as follows:In a live query or dashboard, the
startTime
variable will contain the relative time, such as whereasendTime
will be empty.In a non-live query or dashboard,
startTime
will be the absolute start time when the query was last run.endTime
, similarly, will have the end time of when the query was last run.
Functions
base64Decode()
query function has been updated such that, when decoding to UTF-8, invalid code points are replaced with a placeholder character.The memory usage of the functions
selectLast()
andgroupBy()
has been improved.
Packages
The size limit of packages' lookup files has been changed to adhere to the
MAX_FILEUPLOAD_SIZE
configuration parameter. Previously the size limit was1MB
.For more information, see Exporting the Package.
Bug Fixes
UI Changes
Dashboards and Widgets
Non-breaking space chars (ALT+Space) made Template Expressions unable to be resolved. This issue has been fixed.
Attempting to remove a widget on a dashboard would sometimes remove another widget than the one attempted to remove. This issue has been fixed.
Functions
timeChart()
provided withunit
andgroupBy()
as the aggregation function would not warn on exceeding the defaultgroupBy()
limit
. This issue has now been fixed.The
groupBy()
function would not always warn upon exceeding the defaultlimit
. This issue has now been fixed.
Other
In clusters with bucket storage running queries that take more than 90 minutes, those queries could spuriously fail with a complaint that segments were missing. The issue has now been fixed.