Unomaly 3.0 was released on January 21, 2019.
Introducing the new Unomaly UI
The Unomaly UI has a new layout and navigation.
- Start your investigations from the familiar Situations page or the new Anomalies page by clicking on the relevant tab. The Anomalies page shows you the list of anomalies without the situations grouping.
- Secondary pages such as Knowns, Actions, and Groups management can now be found in a menu on the top right.
- Your user account and profile has it’s own menu also located on the top right.
The in-product tutorial is updated with new content about anomalies and navigation. After you install and log in, take the time to go through the tutorial and see what’s new.
Start your investigation with Anomalies
This release gives you the option of starting your investigations with the anomalies that Unomaly detects. Unlike the Situations view, which shows you related anomalies on a single system, you can use the Anomalies page to search for different anomalies across multiple systems and groups.
To do this, click on the Anomalies tab to see the list of anomalies in your data and start searching and filtering directly from this page. Read more about how to “Investigate anomalies”.
New representation of anomalous events
We’ve changed the way that anomalies are presented in the list on the Situations page and the new Anomalies page.
- Icons to help you identify at a glance the different types of anomalies that were detected in your data.
- A list of systems that produced the event, if it has been seen in more than one system.
- Summary information for each anomaly: first seen, last seen, number of times the event occurred on the system, and the total number of occurrences throughout the infrastructure.
- Capability to copy log messages to search for context external to Unomaly.
- For experimental frequency anomalies, you can see a “Snapshot of event rate” when you expand the event.
New search capabilities
New search capabilities make it possible for you to build better queries to filter Situations and Anomalies. You can now search for multiple values of the same filter type at the same time because they will be OR-ed together in the query. This means that you can search for more than one system, anomaly type, known classification, and so on. Different filter types are combined with AND operations, so that the events have to match all the conditions to be included in the results. Read more about how to “Filter and create views to save workflows”.
- Onboarding data overview was updated to help you choose the input method that best works for your data source. See How to send data to Unomaly.
- Unomaly overview was updated with information about new navigation, Anomalies page, and other new features. See Unomaly 101.
- In this release we have removed the
snmptrapdservices from the product. If you rely on SNMP to get data into Unomaly or for monitoring Unomaly, contact [email protected] for alternatives and migration assistance.
January 30, 2019
- Reduce mongo logging verbosity
January 28, 2019
- Update log rotation settings for /var/log files. They now rotate on a daily basis
- New installations will not use a separate partitions for /var and /opt
- Fix bug where disabled raw events storage would break unomaly-connect
- Fix bug where situation type field would not always be set in the database
January 21, 2019
Unomaly 3.0 includes the following changes:
- Fix issue where the graphs interval would not get updated when using the refresh button
- The techdump generation will now upload the generated techdump to Unomaly support, if possible.
- Fix hostlookup script
- Install fluentd plugins using the unomaly-fluent-gem command
- New backend logic and API endpoints for fetching anomaly details and related anomalies
- The UI now has multiple pages and new navigation.
- Rendering optimizations for the UI.
- Search now supports multiple systems, groups and other conditions. Conditions of the same type will be OR-ed together.
- Added an “Anomalies” page that shows raw anomalies without the “Situation” grouping.
- Updated the “Tutorial” with new information.
- Allow admin users to delete any view
- Moved user-defined fluentd configuration to /DATA/fluentd/etc/conf.d folder
- Toggling event storage between upgrades and using the console menu did not set the correct settings in all services
- New design and representation of anomalies
- You can now expand anomalies to show event details
- Added action menu on anomalies to add knowns and view system details
- Copy log text functionality
- Change to monospace fonts in the situation and anomaly pages
- Migrated system behavior information from mongo to postgres
Did this article help you?
Thank you for the feedback!