Looker Labs features are new, in-progress features, whose details may change over time. They are split into two categories:
- Beta: These features are expected to remain in the product, and errors are expected to be resolved at some point. However, they may change in detail, and errors may not be fixed with the same speed as normal features. The list of current beta Labs features is in this section below.
- Experimental: These features may or may not remain in the product, and errors may or may not be corrected. They are intended to let you know what Looker is thinking about and to get your feedback. The list of current experimental Labs features is in this section below.
You can choose to use these features or leave them disabled. You’ll see a list of these features in the Admin section’s Labs panel. The list of available features may vary, so the feature names and descriptions are blurred in this example:
Each feature has a short description underneath it explaining the functionality that it adds or changes in Looker. If you would like more detail check out the Community Forums, which sometimes have more detailed descriptions, or reach out to Looker support.
Enabling and Disabling Labs Features
To enable or disable a feature, simply click the switch next to the feature name.
Use caution when disabling a Labs feature. If users or developers have relied on the feature to create a certain behavior, disabling the feature will break that functionality.
Current Labs Features
Looker supports the following beta and experimental Labs features.
Beta Labs features are expected to remain in the product, and errors are expected to be resolved at some point. However, their details may change, and errors may not be fixed with the same speed as they would be for normal features.
Allow users to create conditional alerts from their dashboards that trigger an email when the specified conditions have been met or exceeded.
For more information about alerts, see the Alerts documentation page.
Content Curation Beta (Boards)
By participating in this beta, people at your organization will be able to organize existing dashboards and Looks for specific teams or initiatives.
This Labs feature allows users to:
- Create a board for a team or initiative without moving the underlying content stored in folders (formerly Spaces).
- Add context and guide other users with markdown links and descriptions.
- Share the board with other users.
Sandboxed Custom Visualizations
Supports custom visualizations rendered in a sandbox.
Custom visualizations are a community-supported effort. Looker’s support team does not troubleshoot issues relating to custom visualizations or your custom visualization code. For tracking and closing out bugs, please use GitHub issues in the custom visualization’s repository, or visit Looker’s Community Forums for how-to articles, conversations, and tips regarding custom visualizations.
For more information about custom visualizations, see the Visualizations documentation page. To enjoy full functionality of this Labs feature, admins for customer-hosted deploys should make sure you also have installed Chromium.
System Activity Model
Enables the System Activity pages for admins and users with the
see_system_activity permission. The System Activity pages are Explores and dashboards from the Looker internal database that provide data about historical queries and transactions, Looker content usage, Looker user and group activity, and application performance for the Looker instance.
This new model is intended as an enhanced future replacement for the internal i__looker model and legacy usage panel.
Before enabling System Activity on a customer-hosted Looker deployment with MySQL backend, verify that you have properly set up the user for the backend database. Specifically, you must perform the step to
grant all on looker_tmp.* to '<DB_username>'@'%';before enabling the System Activity feature. See the procedure on this documentation page.
When Visual Drilling is turned off, the drill overlay always displays the data table.
When Visual Drilling is enabled, the drill overlay selects the best visualization based on the underlying data, which may be a table visualization or some other visualization type. Or, with Visual Drilling enabled, a drill visualization can be customized by using the
link parameter, as shown on this documentation page and this Help Center article. When the visualization from a drill is not a table, buttons allow the user to switch between the default visualization type and a data table.
For more information about visualization types, see the Visualization Types documentation page.
Experimental Labs features may or may not remain in the product, and errors may or may not be corrected. They are intended to let you know what Looker is thinking about and to get your feedback.
The Custom Fields lab is only visible once you have created a user group called Custom Fields Beta Users. See this documentation page for details.
Lets specific business users create additional, temporary fields on the Explore page that (unlike table calculations) become part of the query running in the database. Other users can see the new fields if given the Explore query’s URL, or if given access to a Look or dashboard that uses that field.
Use the Custom Fields Labs feature if you want to let some of your business users have these capabilities:
- Create semi-permanent measures and dimensions for a one-time or infrequent analysis.
- Create semi-permanent measures and dimensions without needing an analyst.
- Visualize unmodeled data using Instant Explore from the SQL Runner.
Dashboards in Drill Menus
Automatically suggests dashboards with matching filters.
Suggested dashboards will appear in the drill menu. In systems with many dashboards, this feature decreases dashboard performance.
Homepage and Thumbnails Beta
New home page with curated content.
Selecting this option will change what people see when they log in to Looker.
- Instead of landing on a folder, they will now see a homepage that features:
- Thumbnails of dashboards and Looks
- Recently viewed dashboards and Looks
- Suggested dashboards and Looks based on colleagues’ activity
- Updates curated by company administrators
- When working in a folder, people will now see:
- The ability to switch between a grid view or list view of their dashboards and Looks
Dashboards display previous data while new queries are run.
If Instant Dashboards are enabled, when a dashboard loads, Looker pulls data from the cache to immediately display data from the previous run. The dashboard issues new queries that run in the background, and dashboard tiles are then updated as new data is retrieved. The spinner icon appears on the top right of each tile that is still loading, indicating that a query is running in the background and that the currently displayed data is from the last time the query was run. This has the advantage of users not seeing a blank dashboard while it’s loading, but the disadvantage of possibly showing stale data while the new queries run.
Enabling Instant Dashboards also affects how long data is stored in the cache, since this feature relies on the existence of cached data to display.
Local Project Import
A LookML Project can reference files in other locally-maintained projects through the use of the
local_dependency keyword in a manifest file. Enabling this Labs feature is not required to use the
Table-next visualizations offer the following enhancements to traditional Looker table visualizations: subtotals; the ability to freeze columns to the left side of the visualization; and the ability to resize column widths.
See the Table-Next (Beta) Chart Options documentation page for more information.
Trend Lines in Visualizations
Enables the addition of trend lines to Cartesian charts.
This feature enhances the visualization options available for column, bar, line, area, and scatter charts using a variety of regressions.