June 2026
Release notes for June 2026.
Splunk Observability Cloud released the following new features and enhancements in June 2026. This is not an exhaustive list of changes in the Splunk Observability Cloud ecosystem. For a detailed breakdown of changes in versioned components, see the list of changelogs.
What's new
| New feature or enhancement | Description | Release date |
|---|---|---|
| AI Troubleshooting Agent | Splunk Observability Cloud now features an AI troubleshooting agent and remediation plan that automates root cause analysis and provides guided steps to resolve APM and Kubernetes alerts. This tool reduces MTTR by offering integrated impact analysis, evidence, and actionable workflows for customers in the us1 realm using standard, default metrics. See AI troubleshooting agent and remediation plan in Splunk Observability Cloud |
June 17, 2026 |
| Splunk APM |
Monitor the following infrastructure instances from the Instances tab in the service view:
|
June 17, 2026 |
|
As of June 17, 2026, non-histogram Monitoring MetricSets (MMS) are no longer available for new customers. Customers who onboarded prior to this date can still use non-histogram MMS. Existing detectors and charts using non-histogram MMS aren't affected by this change. For more information about MMS, see Learn about Monitoring MetricSets in Splunk APM. |
June 17, 2026 | |
| Kubernetes monitoring |
Monitor the relationships of your Kubernetes instances from the detail view for an instance on the Kubernetes entities page. See Monitor the relationships of a Kubernetes instance. |
June 17, 2026 |
| Notifications |
You can now deactivate alert notifications related to resolution states on an alert rule basis. This helps you to reduce notification noise and focus on active alerts. See Clear alert notifications. |
June 17, 2026 |
| Splunk Secure Application | Use the interactive dashboards on the Runtime vulnerabilities and Attacks tabs to filter security findings by service or infrastructure. | June 17, 2026 |
| Instrument your Node.js and Python applications for Secure Application. | June 17, 2026 | |
| User journey maps in Digital Experience Analytics | User journey maps analyses help you visualize user flows, discover behavioral patterns, and identify friction points. See Create a user journey map. | June 17, 2026 |
| Splunk Synthetics in the AI Assistant | Ask natural-language questions about Synthetic Monitoring tests, downtime configurations, locations, and general monitoring of synthetic tests. See ______ __ _________ __ _____________ _____. | June 17, 2026 |
| Alert Notifications |
You can now include Cc and Bcc recipients for email notifications in Custom Detectors, APM Detectors, Service Level Objectives, and Access Tokens. You can enter multiple recipients in these fields using comma-separated values.Using these fields, you can:
This enhancement improves communication flexibility and ensure that all necessary stakeholders remain informed during incident response and operational monitoring. See Manage notification recipients. |
June 17, 2026 |
|
You can now test and validate a saved webhook integration without triggering a real alert. This feature allows you to verify:
You can reduce the time required to troubleshoot delivery failures across your Splunk Cloud Observability configuration, downstream pipelines, or destination endpoints. See Send alert notifications to a webhook. |
June 17, 2026 | |
| Centralized Role-Based Access Control (RBAC) |
When Splunk Cloud services are unavailable, users can log in through a secondary SAML Identity Provider. This ensures uninterrupted access during maintenance or outages. The system achieves this by using cached capability snapshots or, if those are not available, the default SSO role to grant access. This fallback mechanism allows users to continue working even when the Splunk Cloud service is down, maintaining access continuity and security by matching users through their identity source and email attribute. For more information, see Login and Permission Fallback. |
June 17, 2026 |