Organize streamed data into Assets and Runs

​

Before you begin

• You have a Sift API key and base URL. See Authentication.
• You are already streaming data to Sift, or you are setting up streaming for the first time. See Stream telemetry from a running application.

​

How Assets are created

• Sift creates it automatically the first time data arrives for its name, whether through streaming, file upload, Run creation, or an ingestion config.
• You create it explicitly before any data exists, using the New Asset button on the Assets page or the CreateAsset call on the Asset API. See Create an asset.

​

How Runs work

• start_time, stop_time—the time window of the Run.
• asset_ids—one Run can span multiple assets.
• duration—computed from stop_time - start_time, or ongoing if stop_time is not set.

1. Optional: create the Asset. If it does not exist, Sift creates it when data first arrives.
2. Create a Run.
3. Stream data for an asset, including the Run ID in each request.
4. View the Run in Sift.

​

Create a Run and associate it with streamed data

​

Step 1: Create a Run

​

Step 2: Associate data with the Run

IngestWithConfigDataStreamRequest {
  ingestion_config_id: "<your-config-id>",
  run_id: "<your-run-id>",
  flow: "<flow-name>",
  timestamp: <timestamp>,
  channel_values: [...],
}

​

Verify the result

• The Run listed with its name and start time.
• Channel data visible within the Run’s time window in Explore.

​

Next steps

• Continue streaming across multiple runs
• Stream telemetry from a running application

​

Reference

• Run API reference
• RunService reference
• Runs overview
• Assets overview
• Ingestion config streaming reference