Skip to main content
  • 107 Product updates

Known issues: new pages and updates

New known issue page(s) added: CRIBL-39937 | Cribl Edge on Windows installed in custom directory reverts to default location on upgrade MON-814 | Custom monitors and Data Insights need a namespace filter Known issue page(s) updated: CRIBL-13125 | Pipelines with Clone and other Functions can show inconsistent total processing times CRIBL-13404 | Kubernetes Logs Source doesn't collect logs from exited or short-lived containers CRIBL-13999 | Diag bundles might fail to download from teleported Worker/Edge Nodes CRIBL-14239 | Default commit message missing for non-admin users CRIBL-14627 | Recently added Worker Nodes fail to appear on the Monitoring page CRIBL-15239 | Cannot clear Messages drawer while in GitOps Push mode CRIBL-18973 | Migrated Local Users appear in the Members UI with No Access CRIBL-28742 | Bind error when changing Source address from `0.0.0.0` to `::` on TCP Sources CRIBL-38843 | Pack export in merge mode redacts email notification recipients CRIBL-40418 | Objects named `core` can be excluded from commits CRIBL-40423 | Unattended Cribl Edge upgrade on Windows can cause the host to reboot CRIBL-8600 | GitOps + License expiration = Catch-22 LAKE-1165 | Storage Locations in Cribl.Cloud Government display non-U.S. Regions LAKE-1196 | Lake Dataset IDs must be unique across all Storage Locations LAKE-1368 | Dataset size for Cribl Lake Datasets is not visible in the UI LAKE-2001 | Reserved Dataset ID prefixes for Search lakehouse engines block updates to existing Lake Datasets MON-481 | Insights time range options don't reflect available data SEARCH-12211 | rawMetrics.totalMetrics.eventsIn Can Be Inaccurate for Searches During Concurrent Ingestion SEARCH-12663 | Lakehouse metrics reshape `_metric`/`_value`; searches may fail after upgrade

Related products:Known Issues