Interana release 2.19.0 includes the following new features and resolved issues.
Query API (beta)
Interana’s API gives our customers a way to extract summarized and aggregated data for use in downstream processes, data warehouses, dashboards, or reports. For some customers, Interana is one of several analytics processes they run and consolidation of these various analyses in a single report or dashboard is important. Other customers need aggregated data from Interana to feed into separate processes. With the advent of the API, our customers can now run queries outside of the Interana front end.
The Interana external API is a REST API that allows integration with Interana outside of the standard interface. The API is deployed automatically as part of an Interana cluster upgrade or installation. The first version of the API provides basic query functionality.
See Query API for the detailed reference documentation.
Support for negative data values
We now allow you to display negative values in views, and use negative values in basic, advanced, and compare filters. You can also define derived columns that return negative values.
Support for decimal values
You can now run queries that use decimal values in basic and advanced filters. You can also perform numeric calculations (for example, sum or average) on decimal values in queries.
More timestamp readability improvements
We have improved the readability of timestamps in the Distribution view, and in the exported CSV files for the Time and Table views. The timestamps are now automatically converted from Epoch time to a more readable format.
Improvements to Publishing features
We made some changes to improve the usability of the Publishing features. We have changed the way named expressions (funnels, cohorts, metrics, and sessions) are named, and the names will no longer automatically include the email address of the user who created them. We have added an Owner column that shows you who created the named expression, as well as a Last Modified (By) column to show when the named expression was last edited, and who made the changes.
Automatic calendar alignment for queries
We have changed the default behavior of calendar alignment for queries. When a query’s resolution is greater than one day, the last day of a 1-week, 2-week, 4-week, 13-week, or 52-week time bucket will now end on the day that contains the end time of the query. For example, If the query end time is January 20, 2016 at 2 pm, the weekly time bucket will be end on January 21, 2016 at 12 am for this query, including all of its subqueries.
Note that if your Interana instance is configured to use a specific day as the first day of the week, Interana will not perform this automatic calendar alignment. The instance configuration setting takes precedence over the automatic alignment feature. For example, if your instance is configured to use Monday as the beginning of the week, weeks will always be aligned to run from Monday to Monday.
Resource Usage page (limited release)
The Usage page shows information about your datasets, including data usage and event counts. See Track your data usage for more information.
We added tooltips to the Explorer page. Click the question mark icons to display help topics, with links to more documentation.
We have also added a link to the documentation in the Create/edit derived column window.
Changes to Go button behavior
Previously, changing the View or Dataset in the Query Builder automatically launched a new query. In this release, we have changed this behavior: changing the settings in the Query Builder will not launch queries automatically, giving you the option to change the settings before running the query.
- Editing dashboards: Users were unable to move an existing chart to a new dashboard. This has been resolved.
- Launching queries when you change query values: Changing the View or Dataset automatically launched a new query. We have changed the behavior in this release; changing the settings in the Query Builder will not launch queries automatically, giving you the option to change the settings before running the query.
- Missing timestamp columns: When using the min/max/average/median/distribution measures to build a query, timestamp columns other than the primary timestamp column were not listed. This has been resolved.
- Using text contains with lookup tables: Interana did not allow using "text contains" in filters with lookup tables. This has been resolved.
- Inconsistent date ranges: Exploring from sessions could show graphs with timelines that started before the date of the first data point. This has been resolved.
- Unsupported characters in filters: Including the newline character "\n" in filters would cause an error. This has been resolved.
- Inconsistent Y-axis labels: In some cases, switching views and changing chart controls could cause Interana to display incorrect labels on the Y-axis of charts. This has been resolved.
- Empty Samples query results: In some cases, queries using the Samples view would return no results even if events matched the query parameters. This has been resolved.
- Inconsistent behavior with the Table view: When using the Table view, if you expanded the table by clicking Load, clicking Go would collapse the table again. This has been resolved.
- Inconsistent time query syntax: We have made the syntax consistent for time queries, as described in time query syntax.
- 1 day ago=24 hours ago=1440 minutes ago=86400 seconds ago
- "Yesterday" is mapped to the start of yesterday in the user's timezone (in other words, 00:00:00 yesterday)
- Unsupported options for filters on URL columns: You could not use the "text contains", "starts with", or "ends with" filters with URL columns. This has been resolved.
- Error using typeahead in the filters fields: The "is in cohort" option disappeared if you typed "is in" in the Filter field. This has been resolved.
- Error with ratio measures that included quotes in filter values: If a ratio metric included a filter that used a set of integers in quotes, Interana incorrectly parsed the integers as string values and returned an error when the metric was used in a query. This has been resolved.
- Aggressive rounding for ratio metrics: A change made in a previous release rounded ratio metrics to two decimal places. For metrics that returned a very low percentage, rounding to two decimal places could result in the metric returning 0. This has been resolved.
- Relabeling: Some items have been relabeled for clarity. "Export Chart" has now been relabeled as "Export Data" under Chart Controls. The hover-over labels in funnels now read "From Previous Step" instead of "From Last Step."
- Column headings on Export: We no longer append "number_fields" and "string_fields" when exporting your data to CSV.
Editing a per-actor metric from the Query Builder can clear the Measure field: If you edit a per-actor metric from within the Query Builder and change the Generate previous and next time windows setting, the metric will be cleared from the Measure field. The first entry in the list (typically,
__day__) will be selected. You can then select the per-actor metric that you edited and run the query.