Looker (Google Cloud core) overview

Looker (Google Cloud core) provides simplified and streamlined provisioning, configuration, and management of a Looker instance from the Google Cloud console. Some instance administration tasks may also be performed from the console.

Looker (Google Cloud core) instances are hosted by Google in the Google Cloud. Looker (Google Cloud core) is not available for customer-hosted or multicloud environments.

Looker (Google Cloud core) features

Most Looker (Google Cloud core) functionality is the same as Looker (original) functionality, with a few differences. Learn about Looker (Google Cloud core) features compared to Looker (original), and by edition and network connection.

Functionality that is specific to Looker (Google Cloud core) is documented in the Looker (Google Cloud core) documentation. Functionality that is shared between Looker (Google Cloud core) and Looker (original) is documented in the Looker (original) documentation.

Looker (Google Cloud core) editions

Looker (Google Cloud core) is available in several editions. Each edition type offers different functionality and has different pricing. When you create a Looker (Google Cloud core) instance, you choose the edition that meets your needs. Edition type cannot be changed after instance creation. You can also provision, configure, and manage non-production instances of the same edition types for staging and testing. See the Staging environments and testing section on this page for things to know about setting up a non-production instance.

Standard edition

The Standard edition is tailored for small teams and small or medium-sized businesses with up to 50 internal platform users. In addition to many existing Looker (Google Cloud core) features, the Standard edition brings new functionality, which includes the following:

A Standard edition can be purchased through an annual contract.

Enterprise edition

The Enterprise edition includes all the features of the Standard edition as well as supporting:

An Enterprise edition can be purchased through an annual contract.

Embed edition

The Embed edition includes all the features of the Enterprise edition as well as offering:

An Embed edition can be purchased through an annual contract.

Set up and administer the Looker (Google Cloud core) instance

Before you can explore data, you must create and configure a Looker (Google Cloud core) instance. The process for setting up a Looker (Google Cloud core) instance is as follows:

  1. Ensure that you have the proper Google Cloud console set up by checking the instance creation prerequisites.
  2. Create a Looker (Google Cloud core) instance.
  3. Set up a database connection.
  4. Write LookML.
  5. Add users.
  6. Retrieve and chart data.
  7. Administer the instance from the Google Cloud console and from the Looker (Google Cloud core) instance.

Use the Google Cloud CLI

Throughout the Looker (Google Cloud core) documentation, there are instructions for using the Google Cloud CLI. Install the gcloud CLI to run gcloud CLI commands.

Additionally, refer to the gcloud CLI reference documentation for information about using these commands with Looker (Google Cloud core).

Use Terraform

You can use Terraform to execute some Looker (Google Cloud core) administrative tasks. See the Terraform on Google Cloud documentation for more information about how to provision infrastructure on Google Cloud using Terraform. If you are provisioning resources through the Terraform Google Cloud provider, use version 4.75.0+.

Use the Looker (Google Cloud core) API

View the Looker (Google Cloud core) Admin API reference for information on Looker (Google Cloud core) endpoints for Google Cloud console functionality.

View the Looker API documentation for information on using the API for functionality within a Looker (Google Cloud core) instance.

Types of Looker (Google Cloud core) API calls

The types of API calls that are defined as query API calls are as follows:

  • Calls that are required for automated query pipelines
  • Calls that get data from the client database
  • Calls that run SQL queries or grab results for content

Examples include the following:

The types of API calls that are defined as admin API calls are as follows:

  • Calls that are required to build applications, control content across instances, and perform administrative tasks
  • Calls that control the Looker (Google Cloud core) instance
  • Calls that perform content management, permission and user management, instance administration, or pulling content across folders

Examples include:

There are also other types of API calls, which are ignored for metering purposes, that include calls that perform login, logout, and user authentication tasks.

Release notes and process

Release notes for Looker (Google Cloud core) can be found on the Looker release notes page. To learn about the Looker (Google Cloud core) release process, visit the Looker (Google Cloud core) release overview documentation page.

Pricing

See the Looker (Google Cloud core) pricing page for details about pricing.

Staging environments and testing

If you're interested in using a staging instance, you can create a new non-production instance by using the standard process for creating a Looker (Google Cloud core) instance, and selecting the appropriate non-production edition. The billing for this non-production instance will be the same as for any other Looker (Google Cloud core) instance. See the Looker (Google Cloud core) pricing page for more details.

The types of non-production instance editions are the same as the editions that are available for production instances, and include the following:

The functionalities that are available for each non-production edition are the same as the functionalities that are available for the production editions. Non-production Looker (Google Cloud core) instances also can have the same network connection types as production instances. Having the same functionalities in all environments lets you configure your staging environment to match your production environment, and test updates before deploying to your production instance.

Things to know about non-production Looker (Google Cloud core) instances

The following are things to know about non-production Looker (Google Cloud core) instances:

  • Non-production instances are not covered by any Google SLAs.
  • Horizontal scaling is not considered a non-production use case. If you need to spread instance load and offer specific geographical distribution across multiple Looker (Google Cloud core) instances for your production use case, you will need to purchase additional instances of the existing production Looker (Google Cloud core) edition.
  • Non-production Looker (Google Cloud core) instances cannot be used in lieu of a production instance or for production purposes.
  • All production and non-production Looker (Google Cloud core) instances adhere to the same release cycle. You can configure your non-production instance maintenance settings to match your production instance maintenance settings.

Support

For support with your Looker (Google Cloud core) instance, see the Getting support for Looker (Google Cloud core) documentation page.

What's next