Caught in 4K! New Splunk Features Help Find Problems Faster With Full Visibility of Your Tech Stack

As environments have become more complex and digital user expectations are at an all-time high, organizations are under more pressure than ever to keep their digital systems secure and reliable.

At Splunk, we’ve been hard at work building features that help ITOps and engineering teams thrive amid digital disruptions and build resilient systems. This quarter, we’re excited to announce new Splunk innovations that bring deeper end-to-end visibility into engineering and ITOps teams’ environments, simplifying their investigations and incident analyses. With more flexible data access, visualization capabilities, and enterprise-grade controls, Splunk teams get better context to catch issues earlier and troubleshoot them faster. 

Learn more about our latest and greatest below!

See Across Environments and Stacks in One Place

Splunk’s powerful platform gives practitioners a single and flexible view of their entire digital system. With Splunk, teams get a clear understanding of what exactly is happening in their environment so that when a problem comes up, it’s quickly taken care of.

Faster root cause analysis with observability data in Splunk Cloud Platform: With Related Content for Splunk Cloud Platform, we’re extending a key Splunk Observability Cloud capability which allows engineers and ITOps folks to easily find the right metrics and traces associated with an event in Splunk Cloud Platform. Now, users who go through their logs in Splunk Cloud Platform’s Search and Reporting interface can preview real-time critical application services, infrastructure hosts, and trace context provided by Splunk Infrastructure Monitoring and Splunk APM. 

(Coming Soon) Centralized view of all your service-relevant data: With our new Service-Centric Views in Splunk APM, developers can see all their performance data (metrics, logs, traces) relevant to their service in a single dashboard. This feature enables practitioners to focus more easily on the services that matter to them by clearly visualizing critical service data That way, developers can fully take advantage of Splunk’s powerful telemetry capabilities when analyzing their service health, and accelerate the debugging of their microservices. We’ve also made updates to our Global Search navigation tool to help you find the service you’re looking so you can enjoy a more swift user experience.

Get your data into Splunk faster and easier with Edge Hub: Splunk’s platform provides many ways to help you ingest data. Splunk Edge Hub device is a multi-component solution that includes a hardware device coupled with the Splunk platform and solutions our partners build on top of both. It is a powerful tool that can help collect, distribute, and analyze data from edge devices and sensors, making it easier to capture and act on data that can be difficult to access physically or digitally (for example: Splunk Edge Hub can be deployed on factory floors and indicate outages and downtime in manufacturing processes or the built-in sensors can measure temperature and humidity in a data center.). Today, we’re excited to expand the availability of Edge Hub in the APAC region, giving our APAC customers the ability to easily expand visibility even further to the edge.

Find the Right Balance Between Service Needs and Business Performance

At Splunk, we know how important it is to monitor your Service Level Objectives (SLO) and make sure that your new applications and your end-user experience work seamlessly.  That’s why we’ve built out a new SLO management experience that allows you to create and visualize your SLOs in a more intuitive interface. With this new built-in experience, we’re making it easier than ever for Splunk Observability Cloud users to track the reliability and performance of the services that impact their critical user journeys and business goals.

Simplified SLO Creation: Customers can create Observability SLOs based on a Service Level Indicator (SLI), which are delivered out of the box for the success rate of APM services or can be defined using custom metrics. By choosing a compliance period and a threshold within the SLO creation wizard, users can easily define a target that should be achieved for their services. 

Built-in SLO Alerting: Simple alerting within the UI will help users notify the right people when the error budget is being consumed too quickly or when they have missed your SLO target. Depending on customer needs, alerts can be triggered based on:

• Breach Events – When the SLO target has been missed for the compliance period
• Budget Events – When there might not be enough error budget remaining in the compliance period
• Burn Events – When the recent burn rate indicates a serious incident that could impact their SLO target

Gain Better Control Over Your Observability Platform

Without an extensible and standardized internal developer platform, engineers cannot take advantage of Splunk’s unified visibility and therefore accelerate their mean time to resolve (MTTR) an issue. That’s why we’re launching new functionalities and enterprise-grade controls that enable developers to quickly leverage the full power of Splunk Observability Cloud, and that help platform engineers ensure everyone in the organization is operating efficiently and within budget.

More access control: We’ve expanded our Role-based Access Controls (RBAC) capabilities with two new predefined roles for users: “read-only” (for viewing privileges) and “usage” (which gives access to all data, including subscription usage and billing information). With this release, platform engineers and admins have greater control and flexibility when assigning roles to users in their organizations.

(Coming soon) More cost control: Archived Metrics in Metrics Pipeline Management: As your environments and the amount of telemetry data they emit grow, it becomes increasingly hard to keep your monitoring costs under control. With the release of the “Archived Metrics” tier in Metrics Pipeline Management (MPM), you can redirect and store metrics data that are less time-sensitive (but that you’d still want to keep) into lower-cost storage. That way, you get to ingest and retain all your metrics data while staying within budget, even as you scale. 

More data control: OpenTelemetry Zero Configuration enhancements: Observability Cloud users can now quickly discover and collect metrics from supported third-party applications via the Splunk distribution of the OpenTelemetry Collector without any additional configuration by simply opting into automatic discovery. Additionally, customers can also easily instrument their backend services for APM with just one step with the OpenTelemetry Collector. It’s easy to collect traces, runtime metrics, and profiling data from .NET applications running in Kubernetes environments without any additional configuration.  

• Learn more about Automatic Discovery for Infrastructure Monitoring
• Learn more about Zero Configuration Auto Instrumentation for .NET Backend Services in Kubernetes

We’re excited to show you and talk about these features in person at KubeCon in Europe. Can’t make it there? Check out more about our innovations in our product documentation and official webpage!