This post was originally published on this site

A long time ago, in a datacenter far, far away, application landscapes were easy to visualize, dependencies were simple and free of complexity, and management of these applications was straightforward.

Operation teams had dashboards monitoring metrics like CPU, memory, disk, etc. Mission control rooms were staffed with operators that relied on these dashboards to tell them the overall health of their applications. Since most application landscapes were simple (i.e. load balancer, a couple of web servers, a couple of application pools, maybe a few middleware components and a database), application dependencies were well understood and easy to analyze.

When a CPU would spike (an icon on a dashboard turns red), the operators pretty much knew what impact it would have on the application and the end users. Triage was a no-brainer. Since these “legacy” application landscapes seldom changed from an architecture point of view, understanding dependencies based on correlation worked fine.

Times were easy back then, huh? Fast forward to today. DevOps, agile Application architectures, micro services, containers, 1,000+ services, 100+ 3rd party calls, CDNs, 100+ processes, and plenty of containers. Does the correlation of dependencies work? Can a single person or group of operators analyze all the dependencies for triage? Are dashboards dead? How do I monitor and manage all of this?

Operation teams need monitoring solutions, powered by AI, for triage. Causation, not correlation. Simply ask the monitoring solution what is happening, AI crunches all the dependencies and metrics, and delivers the root cause. So, are dashboards dead? Operation dashboards are indeed dead. Operational-based mission control rooms are no longer needed. Staffing a team to watch dashboards is a distant memory.

More so than ever before, the business stakeholders are demanding greater visibility into the applications that drive their business. They need to understand the end user journey: Are my users frustrated? What is our conversion rate? Is performance impacting revenue? How are my end users interacting with the application? What is their workflow? Sales funnel health? Do I have revenue risk? If so, what is causing that? Was the last marketing campaign successful? This is where BizOps Dashboards enter the scene.

BizOps dashboards are alive and well, and are now in demand more than ever. Since most organizations have many applications, I’ve seen many cases where business stakeholders become overwhelmed with a case of “dashboard explosion”. Far too often, a business stake holder will open the wrong dashboard. Reacting to an internal application that shows a conversion problem caused by authentication errors, and thinking they are looking at an external facing eCommerce application, can be very costly. The business stakeholders need to locate the correct dashboard quickly and understand how the business is performing.

Deploying voice enabled dashboards is the answer. Asking to “Open eCommerce Revenue Dashboard” instead of trying to find that dashboard is so much easier. So, how do you do this?

Watch this short tutorial:

And sign up for your Dynatrace Free Trial

This syndicated content is provided by Dynatrace and was originally posted at