Log streaming: Google BigQuery

      Last updated April 16, 2021

    Fastly's Real-Time Log Streaming feature can send log files to BigQuery, Google's managed enterprise data warehouse.


    Before adding BigQuery as a logging endpoint for Fastly services, you will need to:

    Creating a service account

    BigQuery uses service accounts for third-party application authentication. To create a new service account, follow the instructions in the Google Cloud documentation. Keep the following in mind when creating the service account:

    Obtaining the private key and client email

    When you create the BigQuery service account, a JSON file automatically downloads to your computer. This file contains the credentials for your BigQuery service account. Open the file and make a note of the values of the private_key and client_email fields.

    Enabling the BigQuery API

    To send your Fastly logs to your BigQuery table, you'll need to enable the BigQuery API in the Google Cloud Platform API Manager.

    Creating the BigQuery dataset

    After you've enabled the BigQuery API, follow these instructions to create a BigQuery dataset:

    1. Open the BigQuery page in the Cloud Console.
    2. In the Explorer panel, select the project where you want to create the dataset.
    3. In the details panel, click Create dataset.
    4. In the Dataset ID field, enter a name for the dataset (e.g., fastly_bigquery).
    5. Click the Create dataset button.

    Adding a BigQuery table

    After you've created the BigQuery dataset, you'll need to add a BigQuery table. There are four ways of creating the schema for the table:

    Follow these instructions to add a BigQuery table:

    1. Open the BigQuery page in the Cloud Console.
    2. In the Explorer panel, expand your project and select the BigQuery dataset you created previously.
    3. In the Source section, select Empty Table from the Create table from: menu. The Create table dialog appears.

      The BigQuery create table page

    4. In the Table name field, enter a name for the table (e.g., logs).
    5. In the Schema section of the BigQuery website, use the interface to add fields and complete the schema. See the example schema section for details.
    6. Click the Create Table button.

    Adding BigQuery as a logging endpoint

    Follow these instructions to add BigQuery as a logging endpoint:

    1. Review the information in our Setting Up Remote Log Streaming guide.
    2. Click the Google BigQuery Create endpoint button. The Create a BigQuery endpoint page appears.

      The BigQuery endpoint page

    3. Fill out the Create a BigQuery endpoint fields as follows:
      • In the Name field, enter a human-readable name for the endpoint.
      • In the Log format field, enter the data to send to BigQuery. See the example format section for details.
      • In the Email field, enter the client_email address associated with the BigQuery service account.
      • In the Secret key field, enter the value of the private_key associated with your BigQuery service account.
      • In the Project ID field, enter the ID of your Google Cloud Platform project.
      • In the Dataset field, enter the name of your BigQuery dataset.
      • In the Table field, enter the name of your BigQuery table.
      • In the Template field, optionally enter an strftime compatible string to use as the template suffix for your table.
    4. Click the Advanced options link of the Create a BigQuery endpoint page. The Advanced options appear.

      the advanced options on the create a new BigQuery endpoint page

    5. In the Placement area, select where the logging call should be placed in the generated VCL. Valid values are Format Version Default, None, and waf_debug (waf_debug_log). Selecting None creates a logging object that can only be used in custom VCL. See our guide on WAF logging for more information about waf_debug_log.
    6. Click the Create button to create the new logging endpoint.
    7. Click the Activate button to deploy your configuration changes.

    Example format

    Data sent to BigQuery must be serialized as a JSON object, and every field in the JSON object must map to a string in your table's schema. The JSON can have nested data in it (e.g. the value of a key in your object can be another object). Here's an example format string for sending data to BigQuery:

      "is_tls":%{if(req.is_ssl, "true", "false")}V,
      "cache_status":"%{regsub(fastly_info.state, "^(HIT-(SYNTH)|(HITPASS|HIT|MISS|PASS|ERROR|PIPE)).*", "\\2\\3") }V"

    Example schema

    The BigQuery schema for the example format shown above would look something like this:

    Back to Top