On this page, you will learn about Looker (Google Cloud core) features. Features vary by edition and network configuration .
Feature availability by instance type
The interface and functionality of a Looker (Google Cloud core) instance is virtually indistinguishable from a Looker (original) instance , but the two instance types are not identical. Some differentiating characteristics include the following:
- The administrative functions that are available in the instance Admin section
- The database dialects that the instance can connect to
Administrative compatibility by instance type
All administrative functions and settings for Looker (original) instances are managed in the Admin section of the Looker (original) instance . However, for Looker (Google Cloud core) instances, these settings are divided between the Admin section of the Looker (Google Cloud core) instance and the Google Cloud console .
Database connection compatibility by instance type
The list of supported database dialects that you can connect to your instance differs between Looker (original) and Looker (Google Cloud core).
For a list of database dialects that are supported by Looker (original) instances, see the Looker dialects documentation page.
For a list of database dialects that are supported by Looker (Google Cloud core) instances, see the Connecting Looker (Google Cloud core) to your database documentation page.
Feature compatibility by edition type
Some Looker (Google Cloud core) features vary depending on the instance edition . See the Looker (Google Cloud core) features and entitlements documentation page for more information.
Feature compatibility by network configuration
Looker (Google Cloud core) instances can be configured with one of several network configurations . The following table shows feature compatibility for each network configuration. Select the checkboxes to filter the table.
- Public connections
- Private connections
- Hybrid connections
Conversational Analytics does not support Looker (Google Cloud core) instances that use CMEK or VPC Service Controls.
Connecting a private connections Looker (Google Cloud core) instance that is within a VPC Service Controls perimeter to Conversational Analytics in Looker Studio Pro is not supported and does not meet VPC Service Controls compliance requirements.
- Public connections
- Private connections
- Hybrid connections
Available for the Enterprise and Embed editions.
Not available for the Standard edition.
- Public connections
- Private connections
- Hybrid connections
- Public connections
- Private connections
- Hybrid connections
- Public connections
- Private connections
- Hybrid connections
Available for the Enterprise and Embed editions.
Not available for the Standard edition.
- Public connections
- Private connections
- Hybrid connections
- Public connections
- Private connections
- Hybrid connections
You can connect a Looker (Google Cloud core) instance with any network configuration to customer-hosted Git repositories on the public internet.
If your instance uses a private connections or hybrid connections, you must configure the Google Cloud project to connect to Git.
- Public connections
- Private connections
- Hybrid connections
Custom actions can also be developed for a private action hub server.
Data that your users send by using an action will be passed temporarily from your Looker (Google Cloud core) instance through the Looker Action Hub server.
The Looker Action Hub is disabled by default. To enable an individual action, see the instructions in Admin settings - Actions .
- Public connections
- Public connections
- Public connections
- Private connections
- Hybrid connections
- Public connections
- Private connections
- Hybrid connections
- Public connections
- Private connections
- Hybrid connections
- Public connections
- Private connections
- Hybrid connections
Available for the Embed edition.
Not available for the Standard and Enterprise editions.
- Public connections
- Private connections
- Hybrid connections
