What's new

Learn about what's new in this release of Splunk Cloud Platform.

This page summarizes the new features and enhancements in each release of Splunk Cloud Platform. Use the Version drop-down list to see information for other versions of Splunk Cloud Platform.

The product features deployed in your environment might vary depending on your topology, deployment type, and configuration settings.

Also discover what's new in the following features of Splunk Cloud Platform:

Version 10.8

Learn about what's new in this release of Splunk Cloud Platform.

New feature, enhancement, or change Description

Self-service capability for DMA syncing across search heads and search head clusters

Administrators can now use the new Upload Definition button in the Data Model Editor in Splunk Web to replace an existing data model definition with a JSON file. This is useful when you need matching data model definitions on multiple search heads or search head clusters, such as when differences cause prechecks for data model acceleration summary sharing to fail. For more information, see Upload a data model definition.

Minor usability updates in "Search, Reports & Alerts" page

Minor usability updates in "Search, Reports & Alerts" page.

AI Canvas + Splunk: Knowledge Object search

Users can search their Splunk knowledge objects from within AI Canvas.

Machine Data Lake promotion preview

You can preview a bounded, representative sample of the data and schema that a Machine Data Lake promotion will produce, with faster feedback, safe cancellation, and clear errors before submitting the full job.

Governed approval for Machine Data Lake promotion

Administrators can require review of large or long-lived historical Machine Data Lake promotions, inspect the request context, and approve or deny execution with a durable audit trail.

Validation of cross-cloud support for Federated Search for Splunk

Splunk Cloud Platform now supports federated search in both standard and transparent modes for federated search heads hosted on AWS, Azure, or Google Cloud, and for remote targets hosted on AWS, Azure, or Google Cloud. This support applies to every combination of search head and remote target locations, whether they are hosted on the same cloud provider or on different providers.

Standard mode federated searches are supported in both directions between Splunk Enterprise on premises and Splunk Cloud Platform on Google Cloud or AWS.

Transparent mode federated searches from Splunk Enterprise on premises to Splunk Cloud Platform on AWS, Azure, or Google Cloud are supported. Contact Sales to turn on transparent mode support from Splunk Cloud Platform to Splunk Enterprise on premises. See Cloud provider support for standard and transparent modes in Splunk Cloud Platform.

SVC Usage Attribution and Workload Visibility for Federated Search

Federated Search for Splunk now tags searches that arrive from a federated search head and links the Splunk Virtual Compute (SVC) they use on the remote stack back to the user who ran them.

Federated Search also shows up as its own search type in the Search Workload view in Cloud Monitoring Console. This gives you clear visibility into federated search costs and the information you need to apply workload management policies to those searches. For more information, see Splunk Virtual Compute (SVC) and federated search.

DDAA Restore Permissions Separation

Administrators can delegate DDAA restore monitoring and execution independently from index administration, reducing excess privilege and supporting separation of duties.

Workload Management Controls for Federated Search

Splunk administrators can identify Federated Search workloads executing on remote search heads and apply Workload Management admission rules based on whether the remote work originated from a scheduled or ad hoc search.

These controls help customers protect remote search capacity and critical local workloads by allowing selected federated workloads to be governed without changing existing search syntax or introducing a separate administration workflow. Available with Splunk 10.8 for supported standard and transparent mode Federated Search for Splunk configurations. For more information, see Workload management (WLM) and federated search.

Dynamic Index-based Search Filtering for Federated Search for Splunk

Index-based search filtering for Federated Search for Splunk in transparent mode now includes an optimization that reduces unnecessary system overhead. By default, the federated search head now dynamically learns which indexes are available on each transparent mode federated provider, then sends a search only to providers that have at least one active index. Providers with no active indexes in the search are excluded, which avoids unnecessary searches, optimizes performance, and improves security by keeping searches out of the audit logs on providers that don't hold the target indexes. For more information, see Configure index-based search filtering for transparent mode federated providers.

Indexer CPU Load-Based Protection for Workload Management

Use real-time average indexer CPU load in Workload Management policies to respond to indexer pressure. Administrators can configure CPU load thresholds and trigger supported actions when those thresholds are reached, helping reduce sustained saturation and related performance degradation.

Federated Search - Crawler Error Transparency

Crawler Error Transparency surfaces crawler runtime and configuration errors to customers so they can troubleshoot dataset onboarding and maintenance issues without relying only on backend investigation.

Splunk Cloud - Cisco Data Fabric Evolution (Controlled Availability)

Customers want less friction accessing new capabilities and an opportunity to refine their use cases before engaging with the account team. Splunk Cloud powers the Cisco Data Fabric architecture giving customers included access to new capabilities on each cloud stack, with simple ways to expand usage as needs grow. The launch reduces purchasing friction and preserves familiar pricing paths for cloud customers.

Field schema for federated datasets with external catalogs

Using Catalog APIs, Splunk AI Assistant can now ground federated searches in the actual field names and types of datasets whose schemas live in customer-managed or external catalogs, including CloudWatch Lake, Snowflake, Databricks, and Cisco SAL. Queries are drafted against fields that exist and that you are permitted to access, reducing trial and error on external data.

Field Discovery for Federated Search

Current Federated Analytics searches are restricted to the Statistics tab, hindering immediate data analysis and triaging. This feature aligns the Federated Search experience with traditional Splunk search by enabling the Events tab, field summary sidebar, and timeliner.

The alignment of the Federated Analytics experience with the traditional Splunk native index based search UI, gives you the ability to seamlessly pivot between high-level statistics and granular event data and allows you to leverage the full spectrum of diagnostic tools in one place. This reduces cognitive overhead, accelerates the identification of root causes, triaging the issues at faster pace and ensures that the power of federated search is on parity with native index-based Splunk search experience.

Field extraction and schematization for Machine Data Lake promotion

You can apply supported Splunk props and transforms (P&T) field extractions when promoting Machine Data Lake data to an Analytics Table so the resulting table has selected, queryable fields with a preview that matches the promoted output.

Federated Search for Databricks (Generalized)

Federated Search for Databricks lets customers query Databricks datasets through Splunk across supported hyperscaler deployments. Customers can keep governed data in Databricks while using Splunk search, investigation, and AI-assisted workflows to analyze that data alongside the rest of their machine data estate.

Splunk Cluster-Wide Search Quotas for Admins (Controlled Availability)

Search quotas apply across the entire search head cluster rather than per member, covering both ad hoc and scheduled searches, and are enforced by user role. Administrators get consistent, predictable limits that cannot be bypassed by distributing searches across members, which protects overall system performance in large multi-user environments.

Updates to the connections and datasets REST API endpoint documentation.

The documentation for the /orchestrator/v1/connections and /orchestrator/v1/datasets REST API endpoints has been brought up to date and documentation for a new REST API endpoint (/orchestrator/v1/dataSchema) has been added. The documentation updates cover features added over 10.6, 10.7, and 10.8, including:

  • Support for CloudWatch and Cisco Security Analytics and Logging dataset configurations.

  • Support for filtering dataset listings by dataset status values. Dataset responses now include a processing status.

  • Dataset requests and responses gain fields for the schema ID, source, and last-updated time.

  • The new GET /orchestrator/v1/dataSchemas endpoint supports the predefined schema feature for AWS CloudTrail and VPC Flow Log schemas in AWS S3 federated datasets.

See Endpoints for SPL2 searches, modules, and applications in REST API Reference.