Humio Server 1.46.0 Preview (2022-07-05)
|Version||Type||Release Date||End of Support||Upgrades From||Data Migration||Config. Changes|
Bug fixes and an updated dependency, released to cloud only.
Improvements, new features and functionality
In lists of users, with user avatars containing user initials, the current user would sometimes appear to have an opening parenthesis as their last initial.
New styling of errors on search and dashboard pages.
Improved error messaging of GraphQL queries and mutations for alerts, scheduled searches and actions in cases where a given repository or view cannot be found.
Dashboards and Widgets
The widget legend column width is now based on the custom series title (if specified) instead of the original series name.
Added empty states for all widget types that will be rendered when there are no results.
Heatmapwidget that visualizes aggregated data as a colorised grid.
Pie Chartwidget categories, descending by value. Categories grouped as
Otherswill always be last.
Better handling of dashboard connections issues during restarts and upgrades.
Fix a bug causing Humio's digest coordinator to allow nodes to take over digest without catching up to the current leader. This could cause the new leader to replay more data from Kafka than necessary.
Make a number of improvements to the digest partition coordinator. The coordinator now tries harder to avoid assigning digest to nodes that are not caught up on fetching segments from the other nodes. It also does a better job unassigning digest from dead nodes in edge cases.
Remove remains of default groups and roles. The concept was replaced with UserRoles.
When unregistering a node from a cluster, return a validation error if it is still alive. Hosts should be shut down before attempting to remove them from the cluster. This validation can be skipped using the same
accept-data-lossparameter that also disables other validations for the unregistration endpoint.
Falcon Data Replicator
FDR Ingest will no longer fail on events that are larger than the maximum allowed event size. Instead, such messages will be truncated.
Intermediate network issues are not reported immediately as an error in the UI.
Fixed a bug that could result in merging small ("undersized") segments even if the resulting segment would then have a wider than desired time span. The goal it to not produce segments that span more than the 10% of the retention setting for time for the repository. If no time-based retention is configured on the repository, then 3 times the value of configuration variable
MAX_HOURS_SEGMENT_OPENis applied as limit. For default settings, that results in 72 hours.
Fixed a bug where the
writeJson()function would write any field starting with a case-insensitive
infinityprefix as a null value in the resulting JSON.
Upgrade Kafka to 3.2.0 in the docker images, and in the Humio dependencies.