Cribl Lake 4.20.0
| PRODUCT | DATE | RELEASE | ADDITIONAL RESOURCES |
|---|---|---|---|
| Lake | 2026-09-16 | Feature | Known Issues, Cribl Search Release Notes |
Cribl Lake 4.20.0 supports Dataset Type v2 for DDSS Lake Datasets and raises Dataset limits per Organization. Azure BYOS Storage Locations can set a default retention for every Dataset. Apps are now generally available, and Storage Location pages show DDSS and the default Cribl Lake region more clearly.
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 improvements:
Dataset Type v2 for DDSS Lake Datasets
Cribl Lake Datasets using the DDSS storage format now support Dataset Type v2 in Cribl Search, expanding beyond
previous v1 limits. Set the Dataset Type on the federated Dataset in Search and pair it with a Splunk Journal Datatype
such as splunk_journal.
More Datasets per Organization
Cribl Lake now supports more Datasets per Organization. You can manage retention per Dataset up to 999 Datasets on Managed Lake and Amazon S3 BYOS, and up to 99 Datasets on Azure BYOS. Azure BYOS also supports a default retention setting of 1000 at the storage location.
Storage Location-Wide Retention for Azure BYOS
On an Azure Storage Location, you can set a default retention period for the storage location. New Datasets on that storage location inherit the default retention, and you cannot override it per Dataset. Use this when you want one retention policy for every Dataset in the Storage Location, instead of a lifecycle rule per Dataset.
This does not apply to the default Cribl-managed Lake location, Amazon S3 Storage Locations, Splunk Cloud Self Storage (DDSS), or Netskope. Retention for those remains per Dataset.
Apps General Availability
Apps are now generally available and no longer in Preview.
Apps let you build and run custom applications in Cribl. An App is a packaged user-interface experience that can call Cribl and third-party APIs, enabling tailored workflows and front-end experiences beyond the built-in product surfaces.
This release adds:
- Backend functions: An App can expose HTTP endpoints and run work on a schedule, so it can automate tasks instead of doing everything in the browser.
- External API Access: Administrators can authorize which third-party hosts each App may call, including Organization-specific domains that were not packaged with the App.
- Permissions review: Before you install an App, you can see the in-product permissions and external API access it declares.
- App limits: Administrators can control how much compute and related capacity each App can use.
- Scaffolding and upgrades: App builders get a clearer path from Create App through packaging, versioning, and upgrading an installed App.
Experience Improvements
On the Dataset form, Storage Location lists all available storage locations. Splunk Cloud Self Storage (DDSS) appears as a Storage Location, with its own icon, rather than as a Data format. Creating a Dataset on a Splunk Cloud Self Storage location still stores data in DDSS format.
The default Cribl Lake Storage Location page now matches other locations: the label includes the region (Cribl Lake (
)), a note identifies it as the Organization default.
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.
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: