Create a Monitoring MetricSet (MMS) with up to 5 custom dimensions to filter your data for more detailed monitoring and analysis.

To learn more about multi-dimension MMS and how to use them, see About custom Monitoring MetricSets.

To learn how to create a multi-dimension MMS, see Create a Monitoring MetricSet with custom dimensions.

You can archive and restore histogram metrics through Metric Pipeline Management (MPM), allowing histogram metrics to be stored in real-time and archived data stores. Previously, archiving histogram metrics was not supported. See Introduction to metrics pipeline management.

Monitor your Kubernetes infrastructure with a new experience that includes the following features:

• View or pause real-time Kubernetes data.

• New and customizable columns on the table view to increase visibility into your Kubernetes data. See Customize the table view for Kubernetes entities.

• Improved data density and data visualization on the table view.

• View and filter by OpenTelemetry tags in the table view.

• Enhanced and more intuitive filters in the left navigation panel. See Refine your view with the left navigation panel.

• Monitor Horizontal Pod Autoscaler (HPA) instances with the HPA entity type. To switch between entity types, see Refine your view with the left navigation panel.

• View additional Kubernetes properties in the table and detail view for the following entities:

  • Clusters: API server version, which is retrieved from the kubernetes_build_info control plane metric via Prometheus.

  • Clusters: Kubelet version. This is a node-level property. If there are multiple Kubelet versions within a cluster, all relevant versions are listed.

  • Nodes: Kubelet version.

  • Containers: Container image name and version.

• A newly designed detail view, which now also opens in a flyout panel for in-context navigation instead of a new page.

• View and access the entities related to an instance for enhanced troubleshooting. See View related Kubernetes entities or APM services.

• View and compare YAML configuration files for pods.

• View additional pod statuses. See Monitor Kubernetes pod statuses.

• View all node conditions, including pressure conditions.

The new Kubernetes experience includes the following changes to existing Kubernetes monitoring features:

• The hierarchy map was moved and renamed to the cluster map. See Investigate instances with the cluster map.

• The Overview tab was renamed to the Dashboard tab.

Feature availability depends on your Splunk Distribution of the OpenTelemetry Collector version. Use version 0.138.1 or higher for access to all features. For instructions, see Collector for Kubernetes のアップグレード.

To use the new Kubernetes experience, you must opt in on the user interface. For instructions, see Access the Kubernetes entities page.

The classic Kubernetes navigator experience will be deprecated by February 2026.

Version 0.138.1 includes the following changes related to the new Kubernetes experience:

• For HPA, the target workload property is enabled by default.

• For clusters, the API server version property is enabled by default. The kubernetes_build_info control plane metric is now enabled by default to report API server versions.

• For nodes, the kubelet version property is enabled by default. The new k8s.node.condition metric is enabled by default to report node pressure states.

• For pods, the Quality of Service (QoS) class property is enabled by default. The k8s.pod.status_reason metric is enabled by default to report pod statuses.

• For containers, the new k8s.container.status.reason metric is enabled by default to report container status at the pod level.

• A new configuration is enabled by default to support collecting and displaying pod instance YAML files in the new Kubernetes experience. This configuration enables pod information to be collected and sent to the Splunk Enterprise and Splunk Cloud Platform log endpoint every 6 hours.

For more information on these metrics, see _________ _______ ___ __________ ___ __________.

For upgrade instructions, see Collector for Kubernetes のアップグレード.

• Monitor your PostgreSQL database platforms and correlate the queries they run with the Java applications that those queries come from. To learn more, see Collect data from PostgreSQL.

• View the dependencies and metadata associated with each of your monitored database platforms.

provides detailed application security run-time detection without the need to deploy extra agents through the following key features:

• Run-time vulnerabilities detection with application and risk context.

• Run-time visibility of application libraries with application context.

• Notifications about new vulnerabilities associated with specific environments and services. These notifications can be ingested into Splunk Cloud and Splunk Platform.

To learn more, see Introduction to Splunk Secure Application.

• Configure an Okta SSO integration

• Configure SSO using a generic SAML integration

Assign an org token to the Admin role to ensure streamlined access control and enhanced security for organizational operations. See the following:

• Retrieve and manage user API access tokens using Splunk Observability Cloud

• Custom roles in Splunk Observability Cloud