New in Observability - Improvements to Custom Metrics SLOs, Log Observer Connect & Metrics Pipeline Management

[Teneil_Lawrence]

The latest enhancements to the Splunk observability portfolio deliver improved SLO management accuracy, better cost and data controls, and simplified GDI for new users.

New In Splunk Observability This Month

• SignalFlow Editor for Custom Metrics SLOs
• Log Observer Connect Enhancements - SVC Optimization
• OpenTelemetry Kubernetes Control Plane Metrics
• Token Management Improvements
• Metrics Pipeline Management Updates

Learn More About Each of These Enhancements

SignalFlow Editor for Custom Metrics SLOs

Using the SignalFlow editor, Observability Cloud users now have the ability to create SLOs based on any metric they are monitoring. The SignalFlow editor, which enables users to define data streams for both good and total events, gives users full flexibility and control over their SLI definitions, including the ability to use histogram data. This new feature is available to all Observability Cloud users at no additional cost. 

To create a new SLO, navigate to the Detectors & SLOs section from the left-hand menu in the Observability Cloud platform and select the Service Level Objectives tab. Next, click the Create SLO button to open the wizard and select Custom Metric as the Metric Type.

Log Observer Connect Enhancements - SVC Optimization

With the latest Log Observer Connect improvements, gain more control over your SVC utilization. Decide when you run your log searches with “pause/play” and “run search” buttons, in addition to filters. By default, you’re now limited to 150K logs but you can change to unlimited depending on your needs. To limit further log activities, we’re stopping search jobs triggered by Related Content after 2 minutes of inactivity and after 15 minutes for other sources such as the UI or Field Summary. This functionality is available to Log Observer Connect/Unified Identity customers only.

OpenTelemetry Kubernetes Control Plane Metrics

We’ve enabled the collection of Kubernetes control plane metrics with the OpenTelemetry Prometheus receivers that target specific Prometheus endpoints. Today, control plane metrics are collected with the Smart Agent receiver with the Splunk Distribution of the OpenTelemetry Collector. With this change, you can now collect these metrics for different control plane components with the OpenTelemetry Prometheus receiver instead. This functionality will be automatically available to all Obervability Cloud users who have upgraded to the Splunk distribution of the Collector (v0.109.0+)  by enabling the feature gate useControlPlaneMetricsHistogramData.

Metrics Pipeline Management Updates

• Data retention for Archived Metrics has been extended from 8 to 31 days to facilitate long-term data and historical trend analysis. Users can also customize their specific restoration time windows when creating exception rules for additional flexibility. 
• Additionally, customers can now use Terraform to route metrics to Archived Metrics and create exception rules (select a subset of metrics to route to the real-time tier instead of the archival tier).

Also Coming Soon - Token Management Improvements 

Admin and Power users will now have a new and improved Token Management interface, with Long-Lived tokens, and improved token visibility and rotation, all within a new design aligned with Splunk Cloud.