Login
Contents x
Google BigQuery - Send to Table
  • 16 Mar 2023
  • 3 Minutes to read
  • Print
  • Dark
    Light
  • PDF
Contents

Google BigQuery - Send to Table

  • Updated on 16 Mar 2023
  • 3 Minutes to read
  • Print
  • Dark
    Light
  • PDF

Google BigQuery - Send to Table inserts the entities retrieved from the saved query supplied as a trigger (or devices that have been selected in the asset table) to the supplied Google BigQuery table. When used with a saved query as a trigger, only the fields configured in the saved query are inserted to the supplied table.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

General Settings

  • Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonious. You can change the name according to your needs.
  • Add description (optional) - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
  • Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
  • Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
  • Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.

Connection Settings

Click to view Connection Settings
  1. Table name (required) - The table name.
    • If the table name already exists, new records will be added to that table. If the table schema does not match the query columns, the insertion will fail.
    • If the table name does not exist, a new table will be created and new records will be added to that table. The table schema will be determined based on the query columns.
  2. Project ID (required) - Project ID where the specified table will created.
  3. Dataset ID (required) - Dataset ID where the specified table will created.
  4. JSON Key pair for the service account authentication (required) - A JSON-document containing service-account credentials to GCP, For details, see Connect Axonius to Google Cloud Platform.
  5. Verify SSL (required, default: False) - Verify the SSL certificate offered by Google BigQuery APIs. For more details, see SSL Trust & CA Settings.
    • If enabled, the SSL certificate offered by Google BigQuery APIs will be verified against the CA database inside of Axonius. If the SSL certificate can not be validated against the CA database inside of Axonius, the connection will fail with an error.
    • If disabled, the SSL certificate offered by Google BigQuery APIs will not be verified against the CA database inside of Axonius.
  6. HTTPS proxy (optional, default: empty) - A proxy to use when connecting to the Google BigQuery APIs.
    • If supplied, Axonius will utilize the proxy when connecting to the Google BigQuery APIs.
    • If not supplied, Axonius will connect directly to the Google BigQuery APIs.
  7. HTTPS proxy user name (optional, default: empty) - The user name to use when connecting to the Google BigQuery APIs via the value supplied in HTTPS proxy.
    • If supplied, Axonius will authenticate with this value when connecting to the value supplied in HTTPS proxy.
    • If not supplied, Axonius will not perform authentication when connecting to the value supplied in HTTPS proxy.
  8. HTTPS proxy password (optional, default: empty) - The password to use when connecting to the Google BigQuery APIs via the value supplied in HTTPS proxy.
    • If supplied, Axonius will authenticate with this value when connecting to the value supplied in HTTPS proxy.
    • If not supplied, Axonius will not perform authentication when connecting to the value supplied in HTTPS proxy.

Action Settings

Click to view Action Settings
  1. Append or override the table (required, default: Override) - Select whether to override the table data or to append the table, if already exists, and add new records to it.
    2.Map Axonius fields to Google BigQuery fields (optional, default: empty) - Use the Field Mapping Wizard to map Axonius fields to fields in Google BigQuery. In this way you can transfer data found in Axonius into Google BigQuery. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.
    NOTE

    For details, see Axonius to External Field Mapping.

  2. Partitioning (required, default: No partitioning) - Select whether to create partitioned table for the inserted data:
    • If No partitioning is selected, the table won't be partitioned.
    • If Partition by ingestion time is selected:
      • The table will be partitioned by calendar days.
      • Select whether a partition filter is required. Requiring a partition filter means users must include a WHERE clause that specifies the partitions to query. Using a partition filter may reduce cost and improve performance.

For more details about other Enforcement Actions available, see Action Library.


What's Next
Change password!
Changing your password will log you out immediately. Use the new password to log back in.
Change profile
Success!
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
Logout