On This Page

Home / Stream/ Set Up Cribl Stream/ About Connected Environments/Send Data from On-Prem to Cribl.Cloud

Send Data from On-Prem to Cribl.Cloud ​

Send data from an on-prem deployment to a Cribl.Cloud deployment with a shared auth token on a Cribl HTTP or Cribl TCP Destination and its paired Source. For example, onboard data from on-prem Worker Nodes to Cribl.Cloud Worker Nodes when you move to a Cloud-first or Cloud only solution.

You can transfer data from on-prem Worker Nodes to the Cribl.Cloud Worker Nodes without incurring any data transfer costs.

Auth Tokens are available on every Cribl HTTP and Cribl TCP Source and Destination. To connect an on-prem Leader to Cribl.Cloud for infrastructure management and credit-based billing, see How to Connect On-Prem Leaders to Cribl.Cloud.

Overview of the Data Migration Workflow ​

The workflow for migrating data from on-prem Worker Nodes to Cribl.Cloud Worker Nodes has these phases:

  1. Configure the Destination and Source. Add the same auth token on the on-prem Destination and the Cribl.Cloud Source.

  2. Validate the Data Flow. Confirm that the data is properly flowing from the on-prem Worker Nodes to the Cribl.Cloud Worker Nodes.

Configure the Destination and Source ​

Cribl HTTP and Cribl TCP send data between Cribl nodes without data transfer billing costs. Configure a Destination on an on-prem Worker Group, then configure a Source on a Cribl.Cloud Worker Group.

  1. On the on-prem deployment, select a Worker Group and configure a new or existing Cribl HTTP or Cribl TCP Destination.

  2. In the Auth Tokens section, select Add Token to set up a shared secret between this Destination and the Cribl.Cloud Source.

    • Token secret (text secret): Select an existing text secret. When global secrets are available, select Select local secret or Select global secret first. See Create and Manage Legacy Secrets.
    • Enable token: Toggle on to use this token. Defaults to toggled on.
    • Description: Optionally, enter a description. The description is the token’s name in the list.

    You can add multiple tokens if you need to rotate auth tokens.

  3. Commit and deploy the changes.

  4. On the Cribl.Cloud deployment, select a Worker Group and configure a new or existing Cribl HTTP or Cribl TCP Source. Add the same token. The Token secret (text secret) value must match the secret used on the on-prem Destination.

  5. Commit and deploy the changes.

Validate the Data Flow ​

As a final step, confirm that the data is properly flowing from the on-prem Worker Nodes to the Cribl.Cloud Worker Nodes. A few methods for confirming data flow include:

  • Capture sample data on your Cribl HTTP or TCP Source on your Cribl.Cloud Worker Nodes and verify it looks correct. See Add Sample Data for specific instructions.
  • In the configuration modal for your Cribl HTTP or TCP Source on your Cribl.Cloud Worker Nodes, select the Charts tab to view data events coming in to verify you see activity. You can also compare this to the outgoing data on the Cribl HTTP or TCP Destination on your on-prem Worker Nodes.