News

Devo Product Update 7.17 Released!

Related products: Devo Platform

All of Devo is happy to present Devo Platform release 7.17. This December release comes with two goals! We added two new user-facing functionalities to the platform.  We also made important internal improvements that provide the platform with greater scalability, uniformity and maintainability.

Geo Availability

Region Status
CA Released
US Released
EU Released
APAC Released

 

Table of Contents:

 

Note: EU users are benefiting from double upgrades as all the upgrades in 7.16 are now available to you First!

New Features

 

Data Search

 A new filter allows you to search for a keyword inside of the entire raw event. You can search for a keyword in any of the event fields and it is available in both view modes.

6hi6Q_dB-TKPzp5tG4zZKsPBnwtAtmlYA_eXTLB2-ENAVTaxB3A5Ww0uHgAmWJEeJvmd0WKO0JrqcC0o6ofqmInSrnrp7S6euZGo-j7bWo6bNq-xNksMbu0i2pMRPUED__3zmu9uugUtftNN_SMyzJRKuir91vN5YpVYcTUVJ-pslCNOxWorkkq3viGsPQ

X.509 Certificates

A new column named “Expiration date” is now available. This makes it easier to see if the generated certificates are close to expiration. 

wb66MRH5BT3iZzsayz_VuYTHvV_h2n8tS2yg4k17w-u1NQRmS3Bc2fH8swsf97-SkfmLEYgzFKQpy3RgU0Cf5dzTSan-VHq_hwr36SJal3K2OU8LtI9m6Nfvs6xx9N_lpJZHf1JAQIAhnH6IHiFgx0zPbZgST2GNPY4G27RvC0NzUR4WSHDaAxU_GJR5yA

 

Improvements

 

Lookups

Some Lookups can remain in “Updating”  status for a long time, you can now refresh a lookup that is taking more than 1 hour to be updated. The lookup will then change back to "Available".

Data Search

Sensitivity Filter - We’ve removed the “Sensitivity” filter from the “Create field” and “Filter” tabs in the Operations over fields form. 

Regular Expressions - Functions that require any of its arguments to be regular expressions can now be “regexp” and “str” types.

Depreciated

LINQ Operation MaxMind GeoIPv1 operations are now deprecated. We ask you to use MaxMind GeoIPv2 operations instead.

 

Bug Fixes

Activeboards

Empty Table Widgets - There was a case where the Table widget’s visual tab displayed an empty screen and generated console errors. This only occurred following a specific sequence of steps with a grouping query when it returned no events before the grouping clause. 

Ambiguous Table Widget entries - There was an issue with the Table widget displaying ambiguous values in the exported CSV file when the column values contain commas.

Alerts

XSS - It was possible to insert cross-site scripting in alert annotations. From now on, XSS aren’t allowed.

Roles

Permissions pop up - The pop-up info message for permissions displayed the text without proper margins.

Data Search

Copy Field Names - In List view, if you selected a whole event and copied itregardless of the values for the “Show field names” and “Show null values” togglesthe field names were always missing and the null values were always shown. 

Selecting Events - In List view, with the “Show field names” toggle off, it wasn’t possible to select events. 

Copying Event - In List view, selecting and copying part of an event wouldn’t always result in the copied text matching the selected text.

Expanding Query Editor - If the Query editor was embedded, there were problems expanding it when clicking on it. This was notably problematic because the button to run the query is hidden until the editor is expanded.

Query Editor Reset - There was a problem with the Query editor resetting when the user clicked on the realtime button. 

Group By Error - When a user grouped a query by a non-existent field, the Query editor wouldn’t react. From now on an error will be displayed with the aforementioned field underlined in red. 

Extracting multiple fields - If you opened the JSON parser and selected a number of fields to be extracted, the parser would only extract the first selected field. When editing a breadcrumb that has nested operations, if said breadcrumb didn’t fit in the “Operations over columns” form, then the query editor wouldn’t open. 

Sub Filter Blank - There was a case where, if you ran a second filter you would get a blank screen. This was because the first filter was applied to a non-asterisk field. 

No Operation Called error - Existing Lookups were randomly failing in queries, with an error message “No operation called 

lu/<Lookup_name>/<Lookup_field>”.

 

Link to Release 7.17 Documentation page

Thanks for the updating and publishing the release notes.  It’s good to hear a fix was introduced for the lookup list issue as that is something we encountered and engaged support for.


Yes I heard a few people were affected by that, Good Job Dev Team!