Cribl Stream
Send firewall, identity, endpoint and cloud audit logs from Cribl Stream to nano, one destination and ingest token per source
Connect Cribl Stream to nano to send logs from firewalls, identity providers, endpoints, and cloud audit sources. nano's ingest tokens are bound to one source each, and the token decides the source, so you create one Cribl destination per nano source, each with that source's token, and route events to it.
You need access to edit Cribl Stream's routes and destinations.
Before you start
- You can sign in to nano with the
log_sources:deploypermission. - Every nano source that Cribl will send exists in Ingestion → Log Sources with a published parser. For a format nano has no parser for, create a custom source first (Set up your first feed).
- Know your HEC endpoint:
https://<ingest-host>/services/collector/eventon Self-run, orhttp://<host>:8088/services/collector/eventon open core. Use the full/services/collector/eventpath: open core doesn't serve the bare/services/collector. See HEC. - Use HEC unless you have a reason not to. The Webhook (HTTP JSON) and OpenTelemetry destinations also work; see Other Cribl destinations.
Step 1: Issue one token per source
- In nano, open Ingestion → Log Sources → Credentials.
- Issue a token for each source Cribl will send, with a name such as
cribl-prod-palo-alto. Bind it to that source. - Copy each token when it is shown. It is shown once.
Step 2: Create one HEC destination per source
In Cribl Stream, go to Data → Destinations, pick the HEC-compatible destination, click Add Destination, and enter:
Output ID: nano_palo_alto_traffic
Load balancing: No
HEC endpoint: https://<ingest-host>/services/collector/event
Authentication: Manual
HEC auth token: <token bound to palo_alto_traffic>
Compress: YesRepeat for every source, each with its own token. The event's sourcetype doesn't matter to nano: the token decides where the event lands.
Step 3: Route each source to its destination
Create one route per source, with that source's destination as the output:
| Route | Filter (example) | Output |
|---|---|---|
| Palo Alto | sourcetype=='pan:traffic' || __inputId.startsWith('syslog:pan') | nano_palo_alto_traffic |
| Okta | __inputId.startsWith('rest:okta') | nano_okta |
Put a catch-all route without a nano destination last, so events you did not map aren't sent to a source whose parser doesn't expect them.
Step 4: Verify
- In nano, open Ingestion → Log Sources. The ingest column for each source starts counting within a few minutes of the first events.
- Search for one source:
metadata.log_source="palo_alto_traffic" | head 10- Check that each source's events parse as expected. Fields the parser couldn't map are under
unmapped, and the original line is inraw_data.
Other Cribl destinations
Webhook (HTTP JSON). One destination per source, with that source's token:
Output ID: nano_palo_alto_traffic
URL: https://<ingest-host>/ingest
Method: POST
Format: NDJSON
Compress: Yes
Authentication type: Auth token
Token: <token bound to palo_alto_traffic>OpenTelemetry. For OTLP logs, traces or metrics, use a token bound to an OpenTelemetry source:
Output ID: nano_otlp
Protocol: HTTP
Endpoint: https://<ingest-host>/otlp
OTLP version: 1.3.1
Compression: Gzip
Authentication type: Auth token
Token: <token>On open core, use http(s)://<host>/ingest and http(s)://<host>/otlp. See OpenTelemetry (OTLP).
Troubleshoot
Need help with these checks? Contact support with the deployment, request ID and time with timezone.
| Symptom | Cause | Fix |
|---|---|---|
401 {"text":"Invalid authorization","code":3} | Wrong, truncated, revoked or unbound token | Issue a new token and update the destination. |
| Events land in the wrong source | The destination uses another source's token | Check which source each destination's token is bound to. |
404 | The destination points at the app host (Self-run), or the bare /services/collector path (open core) | Use the ingest host and the full /services/collector/event path. |
| 429 or 503 | Back-pressure | Let Cribl retry; keep persistent queueing on for the destination. |
Revoke a leaked token from Ingestion → Log Sources → Credentials; Vector stops accepting it within seconds.