May 2025
Splunk Observability Cloud released the following new features and enhancements in May 2025. 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.
May 28, 2025 release
|
New feature or enhancement |
Description |
|---|---|
|
Symbolication support |
Splunk RUM now supports symbolication (the translation of raw stack traces back into human-readable form). To use this feature, upload the source map for your browser application, dSYMs for your iOS application, or mapping file for your Android application, and update your Splunk RUM agent. You can either upload these files on-demand or at the time that you update your application with a new version. This feature is not available in the |
|
Updated Splunk RUM agents |
Update your Splunk RUM agent to these versions that support symbolication: |
| Splunk APM and TE linkage | With this release, ThousandEyes users can now have greater visibility into application traces from Splunk APM to improve their mean time to innocence (MTTI) and quickly identify the root cause of incidents. Use this integration to quickly diagnose failing ThousandEyes tests, view trace topology and key service metrics in context of a Thousand Eyes test, and easily set up tests for services instrumented in Splunk Observability Cloud from ThousandEyes. Learn More. |
| Custom roles for Splunk Observability Cloud managed in Splunk Cloud Platform | With this new release, Splunk Cloud Platform admins can tailor what privileges a Splunk Observability Cloud user has for better control, security, and compliance in their workflows. At this stage, admins can control "write/edit" access only (not yet "read" permissions). These custom roles experiences are only available to customers who have set up Unified Identity with centralized user and role management. Learn more. |
| Archived metrics UX improvements | Users can more easily create exception rules and restore historical data of archived metrics within the chart/detector builder UI. Learn more. |
| Utility ranks in usage analytics | New utility ranks in Metrics Usage Analytics reveal exactly where and how each metric is used, providing more insight for archiving or dropping unused data. Learn more. |
| Cross-region pairing for Unified Identity | Customers who have Splunk Observability Cloud and Splunk Cloud Platform organizations in realms us0 or us1 can now pair across regions within AWS regions. This is not a self-service feature. Reach out to your Account team to see if your organizations qualify. Learn more. |
| Client certificate authentication for Synthetics | This feature provides the ability for Synthetic Monitoring users in Splunk Observability Cloud to store and use client certificates in browser, API and HTTP tests for mTLS authentication. This helps to validate security and trust between the Splunk Synthetic agent and your target app or server that requires mTLS authentication, so you can ensure secure, uninterrupted services for your customers. Learn more. |
| Free-text search in embedded logs for APM service-centric view, charts and dashboards, and Kubernetes navigators | For faster troubleshooting and log analysis, customers can now search for specific keywords within logs embedded in APM service-centric view, charts and dashboards, and Kubernetes navigators. To learn more, see the "Search embedded logs" section in Use the service view for a complete view of your service health, Gain insights through chart analytics, and Monitor Kubernetes. |
| Global data links in logs chart details flyout | Global data links are now automatically created and displayed in the logs chart details flyout. You can also configure custom global data links to appear in the logs chart details flyout. See Access global data links from the logs chart details flyout. |
| Page navigation updates | Page headers have been updated across the application to drive a more cohesive experience, and help you to quickly navigate between pages and identify your location in Splunk Observability. |