Unomaly 3.1 was released on February 13, 2019.
Frequency anomalies are live
After some months of testing, frequency anomalies are now automatically enabled for all Unomaly instances. Frequency anomalies detect when the rate of an event spikes (accelerates rapidly) or stops altogether. Read more about How Unomaly detects anomalies and Investigating anomalies.
The settings for frequency anomalies are now available in the general settings, under Advanced.
Unomaly AMI now available on AWS
If you are using Amazon Web Services (AWS), you can quickly launch Unomaly on an EC2 instance using our Unomaly AMI. Read more about how to Install on AWS with the Unomaly AMI.
Anomalies page updates
You can now share anomalies by selecting “Copy link” from the event menu to the right of each event. Selecting this option will copy a dedicated link to the anomaly in your clipboard that you can share with your colleagues.
Our goal is to continue improving the user experience of Unomaly. In this realease, we updated the look of the UI to be more distinctly Unomaly. Take a look and tell us what you think.
- This release includes performance improvements that will impact how Unomaly detects when a system is away. This means that Unomaly will need to relearn systems and you may not see a system away notification until 500k events have been seen for the system.
March 5, 2019
Unomaly 3.1.2 includes the following changes:
- Disable system comeback logic in horizon to avoid hanging transactions
- Fix link to alerts from system tree view
- Fix horizon crashing on postgres null byte errors
February 14, 2019
Unomaly 3.1.1 includes the following changes:
- Fix bug where default compression for system stats was undefined, affecting instance performance
February 13, 2019
Unomaly 3.1 includes the following changes:
- Enable frequency anomalies as default
- Theme enhancements: top- and sidebar colors were changed
- Anomaly sharing functionality added
- Fixed jump to events
- Relogs collection has been removed from mongo (and migrated to postgres)
- Comeback timestamp for anomalies is now exposed through the API
- Fix bug where incorrect creation date of transforms was used in UI
- Fix bug where button to create first user was not disabled after a successful request
- Fix issue where the raw event status in the console menu could be incorrect
Did this article help you?
Thank you for the feedback!