Unomaly 2.30 was released on October 11, 2018.
Configure new installs from the UI
To simplify the install and configuration process, this release introduces a configuration wizard to help you set up your Unomaly instance. The configuration steps include: adding a license to the instance, setting up the email server, and creating the first user.
This means that for first time installs, you only need to use the console menu to configure the instance IP address or host name. Then, you can browse to the instance and complete the configuration from the Unomaly web interface.
Learn Unomaly concepts with the in-app tutorial
New users will now have the option of taking a tutorial when they log into Unomaly for the first time. This tutorial will help users learn how to use the UI and explain the key concepts of Unomaly (such as systems, situations, and knowns). You can run the tutorial at any time from the menu.
Understand the breakdown of anomalies in a situation
We’ve improved the annotation of anomalies in a situation. Now, when you expand a situation you will see an overview of the types of anomalies that make up the situation. For example, the breakdown of events in the situation may include: New event in the entire infrastructure, New event in this system (occurred in others), Frequency spike, and so on.
Try the new experimental scoring on situations
In this release, we are experimenting with a new scoring algorithm that calculates the score for situations based on the amount of anomalies it contains. This differs from the current scoring, which prioritizes new data (such as never before seen events) for higher scores.
The new scoring algorithm should produce fewer high score situations and is less sensitive to tokenization issues. The new scoring algorithm will apply to new detections from the moment you enable the feature. Expect 5-10 days for the algorithm to tune.
See more about the feature and how to enable it in the Experimental Scoring Technical Note.
New documentation for cloud platform installs and data onboarding
New topics to help you:
- Install Unomaly on Google Cloud Platform (GCP) and Microsoft Azure environments.
- Choose how to add data to Unomaly using HTTP API, Fluentd, and Graylog.
This release of Unomaly supports upgrades from Unomaly 2.25. If you are running an earlier version of Unomaly please contact support at [email protected] and we will assist you with your upgrade.
November 6, 2018
Unomaly 2.30.5 includes the following changes:
- Fix issue where backend services could crash and not recover
- Fix issue where transportd could crash when using certain transports
- Fix issue where log output ended up in the console
November 1, 2018
Unomaly 2.30.4 includes the following changes:
- On new installations a number of default views were missing in the UI
- Resolved an upgrade issue from 2.28 to 2.30
- Resolved an installation issue when Unomaly is hosted on Nutanix AHV or Microsoft Hyper-V
- Slack notifications are working again
October 24, 2018
Unomaly 2.30.3 includes the following changes:
- Fix a bug where instance analytics were configured wrongly
- Fix issue with logrotate never rotating logs
- Fixed issue where the installation sometimes grabbed the wrong ip, making it impossible to start the application correctly
October 17, 2018
Unomaly 2.30.2 includes the following changes:
- Migrations from later versions now start migration container correctly.
October 16, 2018
Unomaly 2.30.1 includes the following changes:
- Fix issues on fresh installs
October 11, 2018
Unomaly 2.30 includes the following changes:
- Allow special characters in the username
- Removed the legacy support call-home functionality
- Moved several installation and configuration steps to the UI
- Moved more components of Unomaly into separate docker containers, and adapted all helper applications to be aware of this
- Migrated services to be managed by systemd instead of Supervisord
- Renamed unomaly to unomaly
- Fixed issue where the built-in docker0 bridge could remain after installation
- Added experimental score for situations
- Fixed two rare race conditions in which would lead to a crash/restart of service
- Increased performance of stop detection stage
- Implemented a product tour to guide through core features of the software
- Added introduction tutorial for new users
- Added achievement API for storing user-specific progress & milestones
- Fixed forced session-id change on successful login
- Added a license service for keeping track of license information and allowing online license verification
- Replaced situationd with functionality in other services
- Removed the legacy multi core support, which has been replaced with a different implementation
- Situations now display a summary of the anomalies that it contains
- Moved unomaly syslog-ng to a container, replacing the host syslog with rsyslog for better compatibility with cloud installations. Your existing syslog-ng configuration will still continue to work as intended, but is now separate from the host syslog. No manual intervention is needed.
- You can now reset the password of any user through the console
- The default admin user will not be created on new installs, instead the first user created will be the admin user
- Added optional user interaction metrics
Did this article help you?
Thank you for the feedback!