Send to Google BigQuery Table
  • 2 Minutes To Read
  • Print
  • Share
  • Dark
    Light

Send to Google BigQuery Table

  • Print
  • Share
  • Dark
    Light

The Send to Google BigQuery Table action takes the entities found in the saved query supplied as a trigger (or entities that have been selected in the asset table) and inserts those entities 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.

To configure the Send to Google BigQuery Table action, from the Action Library, click Notify, and then click Send to Google BigQuery Table.

image.png

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.
  9. Instance name (required) - The Axonius node to utilize when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.



For more details on other available Enforcement Actions available, see Action Library.
For more details on Enforcement Set configuration, see Enforcement Set configuration.

Was This Article Helpful?