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.
- 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
metricsDataset in the Dataset configuration. - Add one of the Sources that support metrics, then point your upstream sender at it.
- Prometheus Remote Write: Receives Prometheus metrics from a Prometheus client, or from the Prometheus Destination in Cribl Stream or Cribl Edge. See Ingest Prometheus Metrics into Cribl Search.
- OpenTelemetry: Receives OTLP metrics, logs, and spans. Set Store this source data as to Metrics or Both Logs and Metrics to store the metrics it receives. See Ingest OpenTelemetry Data into Cribl Search.
- Datadog Agent: Receives Datadog metrics, logs, and traces. Set Store this source data as to Metrics or Both Logs and Metrics to store the metrics it receives. See Ingest Datadog Agent Data into Cribl Search.
- Cribl HTTP: Receives native metric events from the Cribl Search Destination in Cribl Stream or Cribl Edge. Set Store this source data as to Metrics or Both Logs and Metrics on the Source, and Send as to Metrics or Logs and Metrics on the Destination. Produce the metric events upstream with a Pipeline - for example, with the Publish Metrics Function. See Ingest Cribl Stream/Edge Data into Cribl Search.
- Route the metrics to the
metricsDataset you want them stored in. By default, a catch-all rule sends all metrics to the primarymetricsDataset. 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.