On This Page

Home /Cribl Insights 4.18.2

Cribl Insights 4.18.2 (Coming Soon) ​

PRODUCTDATERELEASEADDITIONAL RESOURCES
Cribl Insights2026-06-24MaintenanceKnown Issues, Cribl Stream Release Notes

Cribl Insights 4.18.2 adds role-based access control for App Platform (Preview), improves AI provider configuration and security, and includes a breaking Cribl API change that returns HTTP 404 Not Found for single-item GET requests with unknown IDs in Cribl.Cloud.

Important Changes ​

Breaking Change: Single-Item GET Requests Return HTTP 404 for Unknown IDs in Cribl.Cloud ​

In Cribl.Cloud, CRUD-style GET-by-ID operations in the Cribl API now return HTTP 404 Not Found when the requested resource ID does not exist. Previously, those operations returned HTTP 200 OK with an empty items array and count: 0.

This change applies only for unknown resource id values. If a resource id exists but the API cannot return it due to filters, the request still returns HTTP 200 OK with an empty items array and count: 0.

What you need to do:

In Cribl.Cloud, for the affected endpoint paths, update API clients that treat HTTP 200 OK with an empty items array and count: 0 as “not found” to handle HTTP 404 Not Found instead. To confirm that an operation returns HTTP 404 Not Found for an unknown id before updating clients, send a GET-by-ID request with a deliberately invalid id.

Expand the following section for a list of the affected endpoint paths.

List of affected endpoint paths
  • /admin/products/{product}/mappings
  • /alert/monitors
  • /alert/silences
  • /fleet-mappings
  • /lib/grok
  • /lib/mdt-devices
  • /lib/parsers
  • /lib/protobuf-libraries
  • /lib/regex
  • /lib/sds-rules
  • /lib/sds-rulesets
  • /mappings
  • /notification-policies
  • /notifications
  • /pack
  • /products/aetos/config-profiles
  • /products/aetos/monitors
  • /products/aetos/shared-configs
  • /products/lake/lakes/{lakeId}/config
  • /products/lake/lakes/{lakeId}/direct-access
  • /products/lake/lakes/{lakeId}/metrics
  • /search/dashboard-categories
  • /search/dashboards
  • /search/dataset-provider-types
  • /search/datatypes
  • /search/federated_search/engines
  • /search/jobs
  • /search/local_search/dataset-rulesets
  • /search/local_search/datatype-rulesets
  • /search/local_search/engines
  • /search/macros
  • /search/notebook-templates
  • /search/notebooks
  • /search/usage-groups
  • /system/instance
  • /system/internal-groups
  • /system/keys
  • /system/messages
  • /system/policies
  • /system/samples
  • /system/scripts
  • /system/users

New Features ​

App Platform (Preview) RBAC ​

App Platform (Preview) role based access control (RBAC) lets admins control which users and teams can access each App. For each new App, users will see only the Apps that have been shared with them, and admins can grant or revoke access per App.

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 SDKs in their GitHub repositories:

Experience Improvements ​

  • Cribl AI agents on an Anthropic via Amazon Bedrock custom provider now use the AWS SDK’s native outputConfig.text format for structured outputs. Bedrock agents return more reliable schema-valid JSON, and an intermittent ValidationException seen in some agent flows is resolved.

  • You can now update a custom AI provider without re-entering your API key or virtual key. The credential field appears blank in the edit wizard, but Cribl keeps the stored key. Enter a value only to rotate it.

  • Cribl.Cloud now rejects custom AI provider URLs that use a non-HTTP(S) scheme, resolve to localhost, or use a literal private or link-local IP address. This prevents custom providers from probing internal cloud infrastructure.