Configure Cribl Detect
Preview Feature
Cribl is still developing this Preview feature. We don’t recommend using it in a production environment, because the feature might not be fully tested or optimized for performance, and related documentation could be incomplete.
Access requires App Platform, the Cribl Detect feature, and a Role that grants
Apps.Readaccess to the Cribl Detect app.Please continue to submit feedback through normal Cribl support channels, but assistance might be limited while the feature remains in Preview.
Use the Config page to check that Cribl Detect is linked to its lakehouse engine, check the configuration version, and unlink or relink the engine.
To open it, select Config in the Cribl Detect sidebar.
Check the Engine Link
The Status tab shows whether Cribl Detect has a lakehouse engine to work with. When the link is healthy, the Engine tile identifies the linked engine and displays Healthy. The tab also lists:
- The security Datasets that linking created. See What Linking Creates.
- When the link was made.
Configuration Version
The Status tab displays Configuration version, the installed security configuration version, and This release, the version included in the current release. Include the configuration version when you contact Cribl Support.
When an update is available, select Update Configuration. In the Update Configuration? dialog, select Update to update the security configuration to This release. Your detections and enrichment data don’t change.
Manage the Engine Link
Cribl Detect links one lakehouse engine per Organization. To move Cribl Detect to a different engine, unlink the current one and link the new one.
Unlink the Engine
- On Config > Status, under Unlink Engine, set Keep datasets after unlinking:
- Toggle it on to retain stored events, findings, and alerts on the engine.
- Toggle it off to delete the security Datasets.
- Select Unlink Engine.
- Confirm the action:
- If you’re keeping the Datasets, confirm that ingestion is paused and no Dataset rules use the security Datasets, then select Unlink Engine.
- If you’re deleting the Datasets, enter
DELETE, then select Unlink and Delete.
Unlinking detaches the security pipeline from the engine, so Cribl Detect stops evaluating new events. The security Pack and enrichment lookups remain installed whether you keep or delete the Datasets.
Link an Engine Again
After you unlink, Cribl Detect remains available. On Config > Status, under Link Security Engine, select Select Lakehouse Engine, then select an engine in the Ready state.
Cribl Detect runs the same link workflow as the first time. See Link the Engine.
If you kept the security Datasets on a different engine, link that engine instead. See Troubleshooting.
Next Steps
- Get Started: Link an engine and connect Sources.
- Cribl Detect Architecture: How data moves through Cribl Detect.