Cisco builds a unified observability experience between AppDynamics and Splunk

The importance of seamlessly integrated, contextual-rich workflows between observability solutions is critical to operational efficiency. Now Cisco extends the full-stack observability portfolio through a unified observability experience starting with single sign-on (SSO) and deep linking that maintains the context for troubleshooting across AppDynamics and Splunk.

SREs and DevOps engineers often use multiple observability tools for development and troubleshooting. When issues are detected within back-end services, these triaging workflows often require separate logins to switch between solutions in order to zero in on the root cause of an issue, causing friction and user frustration.

Additionally, if multiple tools are used to identify issues, engineers and developers will often have to duplicate their work within these disjointed tools to identify a root cause. This disjointed process is overly complicated, distracting, and downright annoying. Worse, it results in lost productivity and disrupted resource allocation.

Cisco is introducing integrations that enable unified observability experiences that not only simplify user navigation with secure, instant access via SSO, but that also accelerate performance troubleshooting through new deep-linking functionality between AppDynamics and Splunk.

Simplified workflows start with a secure single sign-on

As an engineer, you should not have to log into multiple tools to complete everyday work. A unified and simplified log-in experience streamlines workflows and ensures consistency and usability. SSO authentication improves the productivity of operations and business teams, who can instantly transition between services and products without multiple log-ins.

Using SSO, AppDynamics and Splunk users can log in once and move seamlessly and securely between the two products. To provide industry-leading security, shared credentials across AppDynamics and Splunk, you can use an industry-standard Identity Provider (IdP) platform that supports SAML 2.0 compliance standards such as Okta, DUO, etc.

Deep linking helps maintain context across observability tools

A disjointed workflow can dramatically slow troubleshooting and resolution times. When analyzing performance issues, there is often the need to hand the context and details over from one tool to another for further review. This deep-linking process (i.e., deep linking with Log Observer Connect) provides troubleshooting context between AppDynamics and Splunk. For example, if you identify a performance issue within AppDynamics business transaction, with one click you can quickly jump to the relevant log information associated with that business transaction directly within Splunk without needing search for it and starting your troubleshooting research over again.

Maintaining workflow context during this investigation process can dramatically improve mean time to detect (MTTD) and reduce the mean time to remediate (MTTR), freeing up operations and developer resources while improving application performance and uptime.

Cisco AppDynamics + Splunk = Better Together for Full-Stack Observability

Disjointed tool sprawl is inefficient. Logging into multiple products extends troubleshooting times and consumes additional resources. And maintaining that troubleshooting context is potentially error-prone when traversing tools.

Cisco focuses on three core items:

  1. Unifying the troubleshooting experience.
  2. Improving workflow efficiency.
  3. Maintaining the data context across tools.

The unified observability experience between AppDynamics and Splunk benefits SREs and DevOps by streamlining workflows between two leading full-stack observability products. IT leaders see the immediate benefits of faster ticket resolution, operational productivity, and improved back-end user experience. CIOs can better optimize strategic objectives and enhance overall performance that supports business objectives.

Ensuring a seamless, unified observability experience between AppDynamics and Splunk via SSO and troubleshooting context between tools with deep links that maintain the context of the investigation, enables positive user experiences. Integration and context sharing means that work can be completed more efficiently providing one solution that is best suited for the task.

Learn more:

Register now for the Better Together: Introducing new Splunk integrations and AI innovations for Cisco AppDynamics webinar, where you will learn about new observability and operational efficiency enhancements—from AI innovations to Splunk log analysis solutions for AppDynamics.

In his latest blog, “Bringing the Cisco AppDynamics + Splunk Better Together story to Cisco Live,” Ronak Desai, SVP, GM Cisco AppDynamics and Full-Stack Observability, shares his thoughts on Cisco Live and the AppDynamics + Splunk – Better Together story.

Lastly, these blogs provide additional insights into these recent announcements:

Related Articles

How to Use Observability to Reduce MTTR
Observability
3 Minute Read

How to Use Observability to Reduce MTTR

MTTR (mean time to recovery) is a key performance measurement for any application. Observability helps you reduce MTTR dramatically. Learn how and try it today.
Research Identifies the Clear Benefits of Strong Observability
Observability
3 Minute Read

Research Identifies the Clear Benefits of Strong Observability

Dive into our newly released State of Observability 2021 report to discover how leaders in observability continue to outpace their competitors and have more reliable applications, better performance metrics, and increased ability to innovate.
What the Fastly Outage Can Teach Us About Observability
Observability
5 Minute Read

What the Fastly Outage Can Teach Us About Observability

In this blog post, we discuss the recent Fastly outage, examine how traditional monitoring technologies would have responded to that outage, and show how adopting Digital Experience Monitoring inside your Observability practice is crucial to detecting and responding to these types of issues.
Collecting Kafka Performance Metrics with OpenTelemetry
Observability
7 Minute Read

Collecting Kafka Performance Metrics with OpenTelemetry

Learn how to collect and monitor Kafka performance metrics with Splunk Infrastructure Monitoring using OpenTelemetry — a vendor-neutral and open framework to export telemetry data.
Monitoring Kafka Performance with Splunk
Observability
7 Minute Read

Monitoring Kafka Performance with Splunk

In this three part blog series, we take a deep dive into Kafka architecture, the key performance characteristics that you should monitor and how to collect telemetry data to gain real-time observability into the health and performance of your Kafka cluster using Splunk.
Why You Should Migrate from Legacy Apps to IT Essentials Work
Observability
2 Minute Read

Why You Should Migrate from Legacy Apps to IT Essentials Work

We understand change is never easy, but trust us when we say, migrating from these legacy apps and adopting the new IT Essentials Work (ITE Work) app will be both worthwhile and beneficial.
3 Ways to Upgrade Your IT Strategy with Business KPIs
Observability
3 Minute Read

3 Ways to Upgrade Your IT Strategy with Business KPIs

Get your IT strategy on the right track by focusing on more integrated processes, breaking down team silos and aligning your team objectives to business goals. Check out some practical steps to consider, to maximize value for your organization and customers.
The Hidden Cost of Sampling in Observability
Observability
4 Minute Read

The Hidden Cost of Sampling in Observability

If your observability platform makes you sample, you may be drawing incorrect conclusions from it – resulting in large hidden costs and consequences. Learn more about how you can avoid missing out on critical insights at the most relevant time.
Monitoring Model Drift in ITSI
Observability
4 Minute Read

Monitoring Model Drift in ITSI

In this blog we will talk about some strategies for monitoring your models in ITSI for model drift. This is the idea that the predictive models will become less accurate over time as the rules that were generated originally no longer match the data they are applied to.