Interana release 2.18.0 includes the following new features and resolved issues.
- We have added support for the Microsoft Edge browser.
- You can now set a dashboard as default landing page for all users. All users will see that dashboard when they log in to your Interana instance. Contact Interana to configure this.
- We added quick links to read the product documentation and to email Interana Support. If you have internal documentation about your data, we can also add a link to that documentation. Contact Interana to configure this.
- We have added a notification when you exploring dashboard cached results. Click Go to refresh the query.
- We have added support for LDAP for user authentication. Contact Interana to configure this.
- We have improved the readability of timestamps in Table, Bar, and Pie views. The timestamps are now automatically converted from Epoch time to a more readable format.
We have added publishing features that allow you to:
- Define an authorized group of users to approve and share meaningful metrics, calculations, and views, with their teams
- Minimize visual clutter by removing definitions and pages not strictly shared
- Create personal spaces for users to experiment with building metrics, funnels, dashboards, and other user-generated features
See Publishing settings and permissions for detailed information about configuring and using these features.
Relative time windows
When defining metrics, you can have Interana automatically create previous, current, and next time window metrics. These metrics are auto-created when you select the Generate previous and next time window metrics option in the metrics definition screen.
See Use relative time window metrics for more information about configuring and using this feature.
Advanced filter improvements
You can now use multiple Advanced filters with a query. In addition, you can use Advanced filters when using the Compare filter operation with the Time, Distribution, Bar, and Pie views.
Support for Microsoft Azure data store
We now support data import from Microsoft Azure. This allows us to import files from the Azure blob store, in addition to the existing support for importing files from Amazon S3 and remote file systems.
Switching measures resets the number of groups displayed: Switching the measure from Count Events to Count Unique would reset the Showing Top chart control to its default value. This has been resolved in this release.
YY date format: The import process did not detect dates in the YY syntax. This has been resolved in this release.
Decimals returned in Number view: In some cases, Interana would return decimal values for Count Integers operations in Number view charts. This has been resolved in this release.
Datetime mismatch in Samples view: The time shown for data in Samples view could show incorrect time ranges. This has been resolved in this release.
Filter out error: In some cases, clicking the X icon to filter a group out of an analysis did not work correctly. This has been resolved in this release.
No groupable columns with retention metrics: The first time you created a retention metric on an instance and explore using an automatically generated metric, the Query Builder displays a “No groupable time columns” error. This has been resolved in this release.
Filters and lookup fields: Filtering by “text contains” returned no values for fields in a lookup table. This has been resolved.
Exploring sampled queries from dashboards: Exploring from a chart that was pinned to a dashboard as a Sampled query would open in the Explorer as an Unsampled query. This has been resolved in this release.
Layout issues in tabs: We fixed layout issues in the Cohorts and Metrics tabs that resulted in rows extending beyond the borders of the tables.
32-bit column limitations: Previously, users could not filter to columns with values greater than 32 bits in length. This has been resolved in this release.
Millisecond display: Millisecond values are now displayed without decimals to make them more readable.
Sharing charts: Charts that included filters with the # character could not be shared because the character created an invalid URL. This has been resolved in this release.
Delete cohorts and sessions: In some cases, users could not delete cohorts or sessions. This has been resolved in this release.
Column search: The Search field in the Settings tab did not return columns until you entered two or more characters. This has been resolved in this release.
Missing dashboard charts: Some dashboards shared via email would open without all of the saved charts. This has been resolved in this release.
Y-axis unit inheritance: A secondary y-axis would incorrectly inherit units from the primary y-axis. This has been resolved in this release.
Typeahead field fixes: We have resolved multiple issues related to typeahead fields.
- In some cases, typeahead fields would show no matching values.
- Typeahead fields did not put exact matches at the top of the list.
- Text used in typeahead fields was not cleared after users made a selection.
- The width of typeahead fields would be scaled to match the longest entry in the field. We now truncate very long values in typeahead fields.
- The typeahead filters did not show exact matches at the top of the filtered list.
Derived column fixes: We have resolved multiple issues related to derived columns.
- Derived columns would not appear immediately when viewing the data source.
- Users could not add descriptions for derived columns.
- Users could not create derived columns that used lookup columns.
Columns for Sample view: Users could not select multiple columns to add to the display in Samples view at one time. This has been resolved in this release.
Indicate inactive fields: Fields that couldn’t be edited were not being displayed as inactive (grayed out). This has been resolved in this release.
Time label ordering: Labels for stacked bar charts could be displayed in the wrong order if the query grouped by a time column. This has been resolved in this release.
Inconsistent Go button: In some cases, the Go button would remain active after running a query. This has been resolved in this release.