Skip to main content
Google Cloud Storage is a popular object storage system. This guide demonstrates how to set up Cube to export logs to Google Cloud Storage.

Configuration

First, enable monitoring integrations in Cube.

Exporting logs

To export logs to Google Cloud Storage, start by creating a bucket for Cube logs and a service account that can write to it. Then, put the service account key in an environment variable under Settings → Environment variables, base64-encoded. The name must start with CUBE_CLOUD_MONITORING_ — only variables with that prefix are available to the Vector agent:
Finally, configure the gcp_cloud_storage sink in your vector.toml configuration file. Example configuration:
Commit the configuration for Vector, it should take effect in a minute. Then, navigate to your bucket and watch the logs coming.

Authentication

Authenticate with the credentials_base64 option, referencing the environment variable that holds the base64-encoded service account key, as in the example above. This is the only supported way to give the sink its credentials. See credentials files for how Cube turns the key into a credentials file and how to name the sink.

Healthcheck

The example above sets healthcheck.enabled = false. Vector’s gcp_cloud_storage healthcheck sends a HEAD request to the bucket root, which requires the storage.objects.list permission — write access alone, such as roles/storage.objectCreator, does not grant it. Without this, the sink fails to start with a forbidden-healthcheck error even though it could write objects successfully. With the healthcheck disabled, the sink always starts and reports healthy, so check the bucket itself to confirm that data is arriving.

Exporting Query History

Add the query-history input to the sink to bring Query History export data to the same bucket.
Query History export additionally requires the Monitoring Integrations Tier of your deployment to be set to Medium (Up to 50 GB/mo). On a lower tier it fails silently — the sink reports healthy and the bucket stays empty, with no error logged anywhere.

Troubleshooting

Nothing arrives in the bucket

With the healthcheck disabled, as in the example above, the sink starts and reports healthy even when it can’t authenticate, so check the following:
  • The environment variable referenced by credentials_base64 exists in the deployment and holds a Base64-encoded JSON key. If the value doesn’t decode to JSON, Cube mounts no credentials file and the sink writes nothing.
  • The name of the sink contains only lowercase letters, numbers, and dashes.
  • The service account has a role that allows writing objects to the bucket, e.g. Storage Object Creator (roles/storage.objectCreator).
  • For Query History data, the Monitoring Integrations Tier is set as described in Exporting Query History.
Permission errors for the service account show up in Google Cloud audit logs, not in Cube, if Data Access audit logging is enabled for Cloud Storage. It is off by default.