GCS integration

Data forwarding

The GCS integration lets you forward data to a GCS bucket further analysis. This lets you leverage HUMAN data alongside your existing logs and metrics within your GCS instance. You can use the GCS integration to create a data export or trigger it with a data export action.

Prerequisites

• The GCS bucket service account authentication JSON file
• Appropriate role permissions to create and manage integrations

Integrate with GCS

1. Navigate to Platform Settings > Integrations and click the GCS integration.
2. Click Add Integration.
3. Provide the following:
   • Integration name: How the integration will appear in your HUMAN account.
   • Bucket Name: The name of the GCS bucket to send data to.
   • Service Account Authentication JSON: Upload a JSON file of your service account authentication.
   • Path pattern: The file’s path. This does not affect the file name. See supported path patterns for details.
4. Click Test Connection.
5. Once the test succeeds, click Save changes.

You have successfully configured an GCS integration. Make sure to use the integration to create a data export or trigger it with a data export action.

Supported path patterns

Path patterns allow the following characters:

• a-z
• A-Z
• 0-9
• -, /, !, \, _, ., \, *, ', ()

For example, for the date February 2, 2022, the path pattern would resolve to: 2022/02/16/production/PX12AB34CD.

File name patterns

File names generated by HUMAN follow the following pattern: {guid}_{appId}_{startTimestamp}_{endTimestamp}.

For example, for a file name of 7bd6079a-b5e4-4788-93c5-b939549ce5be_PX3tHq532g_1645014120000000000_1645014180000000000**, the values would be:

• GUID: 7bd6079a-b5e4-4788-93c5-b939549ce5be
• App ID: PX3tHq532g
• Start timestamp (UNIX epoch): 1645014120000000000
• End timestamp (UNIX epoch): 1645014180000000000