Unomaly 2.29 was released on July 11, 2018.
Control access to data with Permissions and Teams
This release includes the ability to limit what data and systems a user can see. Administrators can create teams of users. The data and systems that teams can view and interact with depend on the permissions, which are the groups of systems, assigned to the team. Users can be part of multiple teams to create flexible access rights.
With this feature, you can monitor critical systems without the risk of disclosing sensitive data to unintended users and stay compliant with data regulations, because your users can see only the data they need to and are allowed to see.
Investigate situations faster with the filter bar
In this release, the filter bar gives you the ability to use conditions and free-text search to perform root-cause analysis to explore situations. You can then save your filtered view to monitor your data for future occurrences of the same or similar situations.
Just click on the filter bar to see the options and suggestions, such as: group and system names, types of anomalies, known event tags and classifications. You can also type terms and phrases into the filter bar to quickly filter for situations and specific anomalies based on the text in the events. This feature makes it easier and faster to find answers to followup questions while you investigate problems.
Changes to the Events view
We rebuilt the Events view to focus on the experience of providing context to anomalies (when you “jump to events”), even in cases when there are large volumes of streaming events. The view includes the filter bar, but does not allow free-text search. The view also does not show the timeline or knowns matching.
Changes to the Unomaly API
To support the new search and filtering functionality, we removed the Unomaly API endpoint for situations,
/api/v1/situations. If you need this feature, contact us with your requests.
Before you upgrade
This release includes a database migration to support the new filtering workflows. Depending on the volume of data in the instance that needs to be migrated, users can expect to see an increase in the time it takes to upgrade Unomaly.
Before upgrading to this release, you should back up your instance in case a recovery is needed. Read the upgrade instructions.
- This upgrade will require Unomaly to reboot. The reboot will happen automatically, and the upgrade process will continue unattended after Unomaly restarts. If you log into the console menu, you will see a notice about the upgrade progress and be given a choice to follow the installation process.
- This upgrade process will attempt to allocate disk space automatically for the database migration. If the installer cannot free up enough disk space, it will either prompt you with more suggestions on how to proceed or exit the installation.
September 19, 2018
Unomaly 184.108.40.206 includes the following changes:
- Fix installation issues where deb packages were missing
September 13, 2018
Unomaly 220.127.116.11 includes the following changes:
- Fix issue where free text search in the webui was not working correctly on fresh installs
September 4, 2018
Unomaly 18.104.22.168 includes the following changes:
- Fix issue where an installation could fail if it takes too long
- Fix issue with high CPU load by adding a database index and changing reporting intervals
- Fix issue where actions based on known classification were not executed
August 3, 2018
Unomaly 22.214.171.124 includes the following changes:
- Fix issue where upgrading a manager / worker setup could fail
July 19, 2018
Unomaly 126.96.36.199 includes the following changes:
- Fix issue where techdumps couldn’t be generated in the UI
July 18, 2018
Unomaly 188.8.131.52 includes the following changes:
- Fix issue where the anomalies migration could fail when processing an invalid anomaly
- Fix issue where situationd could crash when processing data for a deleted system
- Fix issue where restarting an upgrade could fail because of a lingering migration container
July 11, 2018
Unomaly 2.29 includes the following changes:
- Add option to autologin when using SAML authentication
- Fix issue where activating a system over the license cap could cause data processing to stop
- Added scroll in the actions-modal of the element is not in view
- Fix issue where empty comments could be posted
- Fix issue where groups could be nameless
- Fix issue where renaming a group did not check if the name was available
- Fix issue where renaming a group could contain illegal characters
- Fix issue where dhcp was still active when setting a static IP
- Fix issue where profiles’ frequency classification was not degraded correctly.
Did this article help you?
Thank you for the feedback!