Organizations today struggle to detect, identify and act on business operations incidents. The gap between business and IT continues to grow, leaving orgs unable to link IT outages to business impact.  Site reliability engineers (SREs) want to understand business impact to better prioritize their work but don’t have a way of monitoring business KPIs. They struggle to link IT outages to business impacts because data is often siloed and knowledge is tribal. It forces teams into a highly reactive mode because they only become aware of the business impact when it’s reported by the business team.

Combining a process orchestration solution like Camunda with an observability solution like IBM Instana can break down these silos, help teams better understand their systems and react faster.

What is Camunda?

Camunda enables process orchestration so that you can fully automate your business processes. Camunda customers are at the forefront of understanding and then digitizing and automating their business workflows.

How do the IT operators (ITOps) or site reliability engineers (SREs) understand the business context of what they see when they monitor Camunda with typical application performance monitoring (APM) observability tools?

The problem with traditional APM observability tools

APM observability tools specialize in leveraging traces, metrics and logs to help IT keep applications healthy and running. These tools typically understand a variety of technologies and can even automatically start monitoring them when an agent is deployed. But most APM observability tools treat automation platforms like Camunda as whatever Java/JEE container they execute within. They fail to provide ITOps or SREs any business context in their normal day-to-day operations.

Combining IBM Instana and Camunda for a fuller picture

Now Instana Observability Business Monitoring from IBM can understand when it’s being used to monitor a Camunda environment and automatically add business-process context to IT traces that ITOps and SREs use for troubleshooting. There is also a business activity view where business processes can be viewed in the context of any IT issues that might be impacting them:

This improvement means that an SRE’s troubleshooting experience goes from seeing traces that only have IT calls like RESTful or database calls to an experience where Instana understands and adds the business process or activity that those calls are implementing:

Optionally, data from the executing activities can be captured along with the trace. Since Instana does not sample trace information, capturing these data can unlock use cases like understanding the true impact of an IT outage.

Camunda and IBM Instana in action

Imagine that Carlos is an SRE whose company is using Camunda. One day, Carlos gets an alert from Camunda that one of the automated activities is stuck. Camunda shows an exception in its log indicating that an external task is failing. Carlos is used to troubleshooting the end-to-end automated processes orchestrated with Camunda in detail but has limited visibility into the issue with the external task.

With Instana monitoring both Camunda and the endpoints implementing those external tasks, Carlos can find the business process or activity within Instana, analyze all of the individual calls within the affected time period and view the end-to-end trace for one of the failing ones. Instana can track calls made to the external endpoint and tell Carlos that there is a database call the external task depends on that is timing out. Now Carlos can focus on getting that database healthy and the activities back on track. 

Learn more

Learn more about how you can effectively use Camunda and IBM Instana together in this on-demand webinar, “Real-Time Business Context for IT. Measure Yourself the Way the Business Measures You.”

Watch the webinar


More from Automation

Real-time transaction data analysis with IBM Event Automation

3 min read - As the pace and volume of digital business continue to increase, organizations are facing mounting pressure to accelerate the speed at which they do business. The ability to quickly respond to shifting customer and market dynamics has become key for contending with today’s growing digital economy. In a survey run by IDC, a leading provider of global IT research and advice, 43% of technology leaders indicated that they were “planning to deliver innovative digital products and services at a faster…

In observability, “automation” is spelled I-N-S-T-A-N-A

3 min read - Modern application environments need real-time automated observability to have visibility and insights into what is going on. Because of the highly dynamic nature of microservices and the numerous interdependencies among application components, having an automated approach to observability is essential. That’s why traditional solutions like New Relic struggle to keep up with monitoring in cloud-native environments.  Automation in observability is a requirement When an application is not performing properly, customers are unhappy and your business can suffer. If your observability…

Debunking observability myths – Part 6: Observability is about one part of your stack

3 min read - In our blog series, we’ve debunked the following observability myths so far: Part 1: You can skip monitoring and rely solely on logs Part 2: Observability is built exclusively for SREs Part 3: Observability is only relevant and beneficial for large-scale systems or complex architectures Part 4: Observability is always expensive Part 5: You can create an observable system without observability-driven automation Today, we're delving into another misconception about observability—the belief that it's solely applicable to a specific part of your stack or…

Buying APM was a good decision (so is getting rid of it)

4 min read - For a long time, there wasn’t a good standard definition of observability that encompassed organizational needs while keeping the spirit of IT monitoring intact. Eventually, the concept of “Observability = Metrics + Traces + Logs” became the de facto definition. That’s nice, but to understand what observability should be, you must consider the characteristics of modern applications: Changes in how they’re developed, deployed and operated The blurring of lines between application code and infrastructure New architectures and technologies like Docker,…