This section provides a high-level description of the new features included in release 3.1:
- Flows enhancements
- Role-based access control (RBAC)
- Sunburst view
- Choose measure in Number view
- Local timezone support
- Export to CSV
- Chart Control options
Flows have been enhanced to allow for higher performance and decreased memory usage. This allows you to run flow queries that are more complex, over greater numbers of events, without exceeding system resources.
Role-based access control (RBAC)
Restricts access to tables based on group membership, similar to the capabilities in Interana 2.x.
Provides sunburst (donut) charts as a query visualization option. Sunburst view has a nesting option that allows you to view two or more concentric sunburst charts together. See Using sunburst charts for more information.
Choose measure in Number view
You can now choose the measure (like "set 2") to display in Number view. Previously in Explorer, the display in Number view was limited to the first measure, which made it inconvenient to show computed measures (like ratios).
Local timezone support
The Interana administrator can now specify a non-UTC time zone for the cluster using the Interana CLI. All times in the GUI are displayed using this time zone.
Export to CSV
You can now download and import raw query results into a spreadsheet.
Chart Control options
Using chart controls, you can now toggle between spline and line visualization in Time view, control number formatting in Number view, and control whether split by fields show up as rows or columns in Table view.
The following issues were resolved in Release 3.1.
|HIG-15082||First and Last for Identifier columns will be supported in 3.1.|
|HIG-14963||When choosing a custom trailing window (which differs from the resolution) in the explorer and running a query that counts actors filtered to the value of a custom actor property, the query may return incorrect results.|
|HIG-14850||When creating an actor property, the preview may issue a query over a different time range than specified in the definition of the actor property. However, the object is still functional and can be used in Explorer.|
|HIG-14830||Spaces and "." will reset your type ahead search, and supported in 3.1.|
|HIG-14478||Splitting a Sankey view query by a set column can cause a query error.|
|HIG-14359||When creating an actor property based on a flow property, the preview may error out. However, the object is still functional and can be used in Explorer.|
|HIG-12236||Referencing set columns within a filter can cause a query error.|
The following are known issues in Release 3.1:
- Board queries are only re-run when you view a board.
- For day_of_week functionality, you must enter it directly into Explorer.
|HIG-14555||Selecting the "is previous to state" flow operator directly from Explorer can cause a query error. To achieve this use case, run a Sankey view query and use the chart interactions.|
|HIG-14937||Splitting a Sankey view query by a DAY_OF_WEEK function expression can cause a query error.|
|HIG-14828||Splitting a Sankey view query by an actor property can cause a query error.|
|HIG-11565||Insufficient system memory can cause flow queries not to complete.|
|HIG-13826||You are unable to show aggregations of both actor properties and event / flow properties within the same query.|
|HIG-14430||Choosing "1 year ago" to "now" in Explorer may not give intuitive results, as it selects the most recent complete year which may not include any recent data. Using "1 year ago exactly" to "now" goes back in time one year from the exact current time. This same distinction exists for all calendar time units.|
|HIG-13763||When using the Edge browser, the trash can icon (to clear a section of the explorer) may not render. However, clicking to the far right of that section will still clear it.|
|HIG-13664||When using the Edge browser, you may need to scroll down to the bottom of the page to see the time scrubber.|
Typing a space in Explorer fields resets the search to anything typed after the space only.
|HIG-13894||You cannot use privacy purge or selective delete on string columns to delete null values.|