Ingest Cribl Stream/Edge Data into Cribl Search
Collect data from your on-prem or Cribl.Cloud tenants to store it in Cribl Search for fast analysis.
Before You Begin
You’ll need:
- A lakehouse engine. See how to get one at lakehouse engines.
- Search Admin Permission, or higher. Learn who can do what at Cribl Search Permissions.
- Cribl Stream or Edge (on-prem or Cribl.Cloud).
- Cribl.Cloud Enterprise for both sides (Cribl Stream/Edge and Cribl Search). For details, see Pricing.
Looking for the Cribl HTTP Source in Cribl Stream instead?
1. Add a Cribl HTTP Source in Cribl Search
On the Cribl.Cloud top bar, select Products > Search > Data > Add Source > Cribl HTTP.
Describe Your Source
Under General, configure:
| Setting | Description | Example |
|---|---|---|
| ID | Source ID, unique across your Cribl.Cloud Workspace. Use letters, numbers, underscores, hyphens. | cribl_stream_prod |
| Description | Describe your Source so others know what it’s for. | Ingests data from Cribl Stream |
| Address | Hostname (FQDN) that Cribl Stream/Edge connects to (Cribl endpoint). | search.main.foo-bar-abc123.cribl.cloud |
| Port | Network port to listen on. Keep the default unless it conflicts with another service. | 10200 (default) |
Set up Authentication (Optional)
For cross-environment or cross-Workspace paths (for example, on-prem Cribl Stream to Cribl Search), you’ll need to set up authentication tokens.
Under Authentication, select Add Token. Add as many tokens as you need.
| Setting | Description | Example |
|---|---|---|
Token secret (text secret) | Reference to a stored secret containing the token. Select a secret or Create a new one. (See Create and Manage Secrets in Cribl Stream). | sec_cribl_stream_token |
| Description | Describe which clients or environments use the token. | Prod Cribl Stream |
Set Up Encryption
Use TLS encryption to protect your data in transit.
TLS must be enabled on both sides (Source and Destination), or disabled on both sides.
Under Encrypt, select Enabled, and set the Minimum TLS version you want to accept.
| TLS Version | When to Use |
|---|---|
| 1.3 | Recommended. Provides the best security. |
| 1.2 | Use only when connecting to older systems that don’t support TLS 1.3. |
| Older than 1.2 | Avoid if possible. These versions are no longer considered secure. |
Select Save to create the Source.
2. Set Datatype Rules
Configure Datatype rules to parse, filter, and normalize your data into structured fields. We call this process Datatyping.
On the Cribl.Cloud top bar, select Products > Search > Data > Datatyping (auto). Here, you can:
- Use Auto-Datatyping to parse your data automatically.
- Check for uncategorized data that didn’t match any Datatype rules.
- Handle the uncategorized data by adding custom Datatype rules.
See also:
- Datatypes in Cribl Search
- v2 Datatypes in Cribl Search
- List of Stock v2 Datatypes
- Add a Custom v2 Datatype
3. Set Dataset Rules
Configure Dataset rules to organize the parsed events into Datasets. This also determines how long the data is kept, as each Dataset has its own retention period.
On the Cribl.Cloud top bar, select Products > Search > Data > Datasets: Organize Your Data, and see Organize Your Data for details.
4. Add a Cribl Search Destination in Cribl Stream or Edge
For Stream, see Cribl Search Destination in the Stream docs.
For Edge, see Cribl Search Destination in the Edge docs.
5. See Live Data Flow
Verify that events are successfully flowing from your HTTP client into Cribl Search.
On the Cribl.Cloud top bar, select Products > Search > Data > Live Data.
Here, check for your Cribl HTTP Source. For details, see See Live Data Flow.
Next Steps
Now that your data is in Cribl Search, you can start using it. For example: