Cribl Insights 4.20.0 ​

Cribl Insights 4.20.0 adds Permissions for Insights and its sub-products. Muting Rules can now target a specific alert instance or matching tags. System Insights adds lakehouse engine and usage visualizations. You can also clone Monitors and use a simpler Insights step when adding a Workspace.

Important Changes

This release introduces breaking changes and deprecations that require action if you use the affected features:

• New location for Login and SSO/SLO callback rate limits
• Notice: Cribl as Code TypeScript and Go SDK Discontinuation
• Review the full list of important changes for additional critical updates.

New Features ​

This release provides the following new features:

Permissions on Cribl Insights ​

You can now grant Permissions to Members and Teams on Cribl Insights and the System Insights, Data Insights, and Alerts sub-products. Organization Admins and Workspace Owners and Admins inherit full access to Insights and sub-products. For other Members, assign Cribl Insights Permissions. See Insights Permissions for more details.

Target Muting Rules by Alert Instance and Tags ​

Muting Rules can narrow a mute below the Monitor level. A rule still anchors to exactly one Monitor, but you can add:

• Alert Instance ID to mute a single alert instance of that Monitor.
• Tags to mute only the instances whose alert labels match, using the same tag-matching model as alert-label routing.

See Muting Rules for more information.

System Insights: Lakehouse Engine and Usage Visualizations ​

System Insights adds visualizations for lakehouse engine utilization, so you can see backpressure and queueing without inferring them from query behavior:

• A new Lakehouse Engines tab with expandable Infrastructure and Volume sections, and an Engine filter that scopes panels to a single engine. Infrastructure adds Pre-processing Load, the capacity utilization of the compute that pre-processes events on their way into your engines. It also adds CPU Utilization by Workload, which stacks engine CPU by workload, and Backpressure, which plots one series per engine on a two-state Not Backpressured or Backpressured axis. Volume collects the panels that were previously on the Search Volume tab, which is removed, and adds an Inbound Data Volume chart.
• A new Usage tab that holds the existing CPU*Hours panel, moved off the Overview tab.
• Avg Queue Time by Compute Type and Avg Time to First Byte by Compute Type panels on the Overview tab, so you can see how long searches wait before execution and how quickly the first results arrive. Avg Search Duration by Compute Type replaces the Search Duration Distribution histogram.

These tabs require the Read Only, Editor, or Admin Permission on the System Insights sub-product. See System Insights.

Experience Improvements ​

• You can now clone a default or custom Monitor and use its configuration as the starting point for a new one, from either the row actions menu or a multi-select at the bottom of the Monitors page. Every clone is created as a custom Monitor, named with the original name plus -clone, or -clone-<next available number> if that name is taken.
• When you create a new Workspace in Cribl, the new Add Workspace flow simplifies the Insights step, reducing the choices you make while creating a Workspace.

Important Changes ​

New Location for Login and SSO/SLO Callback Rate Limits ​

The Login rate limit and SSO/SLO callback rate limit settings moved to Settings > Global > General Settings > Limits > API for the Leader and to Worker Group/Fleet Settings > Limits > API for Worker Groups and Edge Fleets. Cribl stores the values in api-limits.yml. Existing rate limits defined in cribl.yml continue to work and do not need to be migrated. To set the limits using the Cribl API, use the PATCH /system/api-limits endpoint.

Notice: Cribl as Code TypeScript and Go SDK Discontinuation ​

Cribl is stopping active development of the Cribl as Code Go and TypeScript SDKs, which were previously in preview. To give existing users a clear path forward, we are moving the SDKs from the criblio GitHub Organization to the Cribl Community GitHub Organization. We are also open sourcing them as community resources. Customers and community members can continue using and building on the SDKs while Cribl steps back from active development and long-term support.

The SDKs will continue to be available through their new home in the Cribl Community GitHub Organization. You can continue using, forking, and extending them based on your needs. To use a supported integration, consider migrating to the Python SDK, Terraform Provider, or direct Cribl API access. During the transition period, Cribl support will be limited to critical issues, such as security vulnerabilities or P0 blockers. On October 1, 2026, the SDK repositories will be archived and marked read-only.

Corrections ​

SDK Changelogs ​

The Cribl SDKs help you integrate with Cribl and reduce the need for repetitive tasks. We maintain changelogs for each version of the Cribl Python SDKs in their GitHub repositories:

• Control plane
• Management plane