On This Page

Home / Search/ Metrics (Preview)/Ingest Metrics into Cribl Search

Ingest Metrics into Cribl Search ​

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.

Please continue to submit feedback through normal Cribl support channels, but assistance might be limited while the feature remains in Preview.

Get metrics into Cribl Search, so you can explore and alert on them alongside your logs.


Before You Begin ​

Before you can explore metrics, you need to get metrics into Cribl Search. Metrics are stored on a lakehouse engine, the same compute and storage that accelerates your logs.

  1. Add a lakehouse engine to store and accelerate your metrics. See Lakehouse Engines in Cribl Search. You can change the default 365-day Retention period on the metrics Dataset in the Dataset configuration.
  2. Add one of the Sources that support metrics, then point your upstream sender at it.
  3. Route the metrics to the metrics Dataset you want them stored in. By default, a catch-all rule sends all metrics to the primary metrics Dataset. To target a different engine’s Dataset, add a rule that matches the Source. See Add Metric Dataset Rules.

Metrics is a Preview feature. Adding metrics to a production lakehouse engine can affect its performance. Until the impact is better understood, use one of these approaches:

  • On a production engine, keep the metrics volume small.
  • Give metrics a dedicated engine, so their load doesn’t compete with production search. You can route a metrics Source to a dedicated engine with Metric Dataset rules.

Next Steps ​

After your metrics are flowing, open the Metrics Explorer to explore them.