Sunday, June 23, 2024
HomeHealthy LivingFixing Information Wrangling for Dashboards

Fixing Information Wrangling for Dashboards

This put up is about Dashify, the Cisco Observability Platform’s dashboarding framework. We’re going to describe how AppDynamics, and companions, use Dashify to construct customized product screens, after which we’re going to dive into particulars of the framework itself. We are going to describe its particular options that make it essentially the most highly effective and versatile dashboard framework within the business.

What are dashboards?

Dashboards are data-driven consumer interfaces which can be designed to be seen, edited, and even created by product customers. Product screens themselves are additionally constructed with dashboards. Because of this, an entire dashboard framework gives leverage for each the top customers seeking to share dashboards with their groups, and the product-engineers of COP options like Cisco Cloud Observability.

Within the observability area most dashboards are centered on charts and tables for rendering time collection knowledge, for instance “common response time” or “errors per minute”. The picture beneath exhibits the COP EBS Volumes Overview Dashboard, which is used to know the efficiency of Elastic Block Storage (EBS) on Amazon Internet Providers. The dashboard options interactive controls (dropdowns) which can be used to further-refine the state of affairs from all EBS volumes to, for instance unhealthy EBS volumes in US-WEST-1.



A number of different dashboards are supplied by our Cisco Cloud Observability app for monitoring different AWS methods. Listed below are only a few examples of the quickly increasing use of Dashify dashboards throughout the Cisco Observability Platform.

  • EFS Volumes
  • Elastic Load Balancers
  • S3 Buckets
  • EC2 Cases

Why Dashboards

No observability product can “pre-imagine” each means that prospects wish to observe their methods. Dashboards permit end-users to create customized experiences, constructing on current in-product dashboards, or creating them from scratch. I’ve seen giant organizations with greater than 10,000 dashboards throughout dozens of groups.

Dashboards are a cornerstone of observability, forming a bridge between a distant knowledge supply, and native show of knowledge within the consumer’s browser. Dashboards are used to seize “situations” or “lenses” on a selected drawback. They’ll serve a comparatively fastened use case, or they are often ad-hoc creations for a troubleshooting “conflict room.” A dashboard performs many steps and queries to derive the information wanted to handle the observability state of affairs, and to render the information into visualizations. Dashboards might be authored as soon as, and utilized by many various customers, leveraging the know-how of the writer to enlighten the viewers. Dashboards play a vital position in low-level troubleshooting and in rolling up high-level enterprise KPIs to executives.


The aim of dashboard frameworks has at all times been to offer a means for customers, versus ‘builders’, to construct helpful visualizations. Inherent to this “democratization” of visualizations is the notion that constructing a dashboard should one way or the other be simpler than a pure JavaScript app improvement method. Afterall, dashboards cater to customers, not hardcore builders.

The issue with dashboard frameworks

The diagram beneath illustrates how a standard dashboard framework permits the writer to configure and organize parts however doesn’t permit the writer to create new parts or knowledge sources. The dashboard writer is caught with no matter parts, layouts, and knowledge sources are made obtainable. It’s because the areas proven in purple are developed in JavaScript and are supplied by the framework. JavaScript is neither a safe, nor straightforward know-how to be taught, subsequently it’s not often uncovered on to authors. As a substitute, dashboards expose a JSON or YAML primarily based DSL. This usually leaves area groups, SEs, and energy customers within the place of ready for the engineering workforce to launch new parts, and there may be virtually a deep function backlog.


I’ve personally seen this state of affairs play out many occasions. To take an actual instance, a workforce constructing dashboards for IT companies needed rows in a desk to be coloured in response to a “warmth map”. This required a function request to be logged with engineering, and the core JavaScript-based Desk element needed to be modified to assist warmth maps. It turned typical for the core JS parts to develop into a mishmash of domain-driven spaghetti code. Finally the code for Desk itself was onerous to seek out amidst the handfuls of props and hidden behaviors like “warmth maps”. No one was proud of the state of affairs, however it was typical, and core element groups principally spent their dash cycles constructing area behaviors and making an attempt to know the spaghetti. What if dashboard authors themselves on the power-user finish of the spectrum may very well be empowered to create parts themselves?

Enter Dashify

Dashify’s mission is to take away the barrier of “you may’t do this” and “we don’t have a element for that”. To perform this, Dashify rethinks a number of the foundations of conventional dashboard frameworks. The diagram beneath exhibits that Dashify shifts the boundaries round what’s “inbuilt” and what’s made fully accessible to the Writer. This radical shift permits the core framework workforce to deal with “pure” visualizations, and empowers area groups, who writer dashboards, to construct area particular behaviors like “IT warmth maps” with out being blocked by the framework workforce.


To perform this breakthrough, Dashify needed to resolve the important thing problem of easy methods to simplify and expose reactive habits and composition with out cracking open the proverbial can of JavaScript worms. To do that, Dashify leveraged a brand new JSON/YAML meta-language, created at Cisco within the open supply, for the aim of declarative, reactive state administration. This new meta-language is known as “Acknowledged,” and it’s getting used to drive dashboards, in addition to many different JSON/YAML configurations inside the Cisco Observability Platform. Let’s take a easy instance to point out how Acknowledged permits a dashboard writer to insert logic instantly right into a dashboard JSON/YAML.

Suppose we obtain knowledge from an information supply that gives “well being” about AWS availability zones. Assume the well being knowledge is up to date asynchronously. Now suppose we want to bind the altering well being knowledge to a desk of “alerts” in response to some enterprise guidelines:

  1. solely present alerts if the share of unhealthy cases is bigger than 10%
  2. present alerts in descending order primarily based on proportion of unhealthy cases
  3. replace the alerts each time the well being knowledge is up to date (in different phrases declare a reactive dependency between alerts and well being).

This snippet illustrates a desired state, that adheres to the foundations.



However how can we construct a dashboard that constantly adheres to the three guidelines? If the well being knowledge adjustments, how can we ensure the alerts will probably be up to date? These questions get to the guts of what it means for a system to be Reactive. This Reactive state of affairs is at finest tough to perform in at the moment’s widespread dashboard frameworks.

Discover now we have framed this drawback by way of the information and relationships between totally different knowledge gadgets (well being and alerts), with out mentioning the consumer interface but. Within the diagram above, be aware the “knowledge manipulation” layer. This layer permits us to create precisely these sorts of reactive (change pushed) relationships between knowledge, decoupling the information from the visible parts.

Let’s take a look at how straightforward it’s in Dashify to create a reactive knowledge rule that captures our three necessities. Dashify permits us to exchange *any* piece of a dashboard with a reactive rule, so we merely write a reactive rule that generates the alerts from the well being. The Acknowledged rule, starting on line 12 is a JSONata expression. Be at liberty to strive it your self right here.


One of the fascinating issues is that it seems you don’t should “inform” Dashify what knowledge your rule relies on. You simply write your rule. This simplicity is enabled by Acknowledged’s compiler, which analyzes all the foundations within the template and produces a Reactive change graph. In the event you change something that the ‘alerts’ rule is taking a look at, the ‘alerts’ rule will fireplace, and recompute the alerts. Let’s rapidly show this out utilizing the acknowledged REPL which lets us run and work together with Acknowledged templates like Dashify dashboards. Let’s see what occurs if we use Acknowledged to vary the primary zone’s unhealthy depend to 200. The screenshot beneath exhibits execution of the command “.set /well being/0/unhealthy 200” within the Acknowledged JSON/YAML REPL. Dissecting this command, it says “set the worth at json pointer /well being/0/unhealthy to worth 200”. We see that the alerts are instantly recomputed, and that us-east-1a is now current within the alerts with 99% unhealthy.


By recasting a lot of dashboarding as a reactive knowledge drawback, and by offering a strong in-dashboard expression language, Dashify permits authors to do each conventional dashboard creation, superior knowledge bindings, and reusable element creation. Though fairly trivial, this instance clearly exhibits how Dashify differentiates its core know-how from different frameworks that lack reactive, declarative, knowledge bindings. In actual fact, Dashify is the primary, and solely framework to function declarative, reactive, knowledge bindings.

Let’s take one other instance, this time fetching knowledge from a distant API. Let’s say we wish to fetch knowledge from the Star Wars REST api. Enterprise necessities:

  1. Developer can set what number of pages of planets to return
  2. Planet particulars are fetched from star wars api (
  3. Listing of planet names is extracted from returned planet particulars
  4. Person ought to be capable to choose a planet from the checklist of planets
  5.  ‘residents’ URLs are extracted from planet data (that we obtained in step 2), and resident particulars are fetched for every URL
  6. Full names of inhabitants are extracted from resident particulars and offered as checklist

Once more, we see that earlier than we even contemplate the consumer interface, we are able to forged this drawback as an information fetching and reactive binding drawback. The dashboard snippet beneath exhibits how a worth like “residents” is reactively certain to selectedPlanet and the way map/scale back model set operators are utilized to complete outcomes of a REST question. Once more, all of the expressions are written within the grammar of JSONata.


To display how one can work together with and check such a snippet, checkout This github gist exhibits a REPL session the place we:

  1. load the JSON file and observe the default output for Tatooine
  2. Show the reactive change-plan for planetName
  3. Set the planet identify to “Coruscant”
  4. Name the onSelect() perform with “Naboo” (this demonstrates that we are able to create features accessible from JavaScript, to be used as click on handlers, however produces the identical end result as instantly setting planetName)

From this concise instance, we are able to see that dashboard authors can simply deal with fetching knowledge from distant APIs, and carry out extractions and transformations, in addition to set up click on handlers. All these artifacts might be examined from the Acknowledged REPL earlier than we load them right into a dashboard. This outstanding financial system of code and ease of improvement can’t be achieved with another dashboard framework.
In case you are curious, these are the inhabitants of Naboo:


What’s subsequent?

We’ve proven a number of “knowledge code” on this put up. This isn’t meant to suggest that constructing Dashify dashboards requires “coding”. Reasonably, it’s to point out that the foundational layer, which helps our Dashboard constructing GUIs is constructed on very strong basis. Dashify not too long ago made its debut within the CCO product with the introduction of AWS monitoring dashboards, and Information Safety Posture Administration screens. Dashify dashboards are actually a core element of the Cisco Observability Platform and have been confirmed out over many advanced use instances. In calendar Q2 2024, COP will introduce the dashboard enhancing expertise which gives authors with inbuilt visible drag-n-drop model enhancing of dashboards. Additionally in calendar Q2, COP introduces the power to bundle dashify dashboards into COP options permitting third social gathering builders to unleash their dashboarding expertise. So, climate you skew to the “give me a gui” finish of the spectrum or the “let me code” life-style, Dashify is designed to fulfill your wants.

Summing it up

Dashboards are a key, maybe THE key know-how in an observability platform. Present dashboarding frameworks current unwelcome limits on what authors can do. Dashify is a brand new dashboarding framework born from many collective years of expertise constructing each dashboard frameworks and their visible parts. Dashify brings declarative, reactive state administration into the palms of dashboard authors by incorporating the Acknowledged meta-language into the JSON and YAML of dashboards. By rethinking the basics of knowledge administration within the consumer interface, Dashify permits authors unprecedented freedom. Utilizing Dashify, area groups can ship advanced parts and behaviors with out getting slowed down within the underlying JavaScript frameworks. Keep tuned for extra posts the place we dig into the thrilling capabilities of Dashify: Customized Dashboard Editor, Widget Playground, and Scalable Vector Graphics.

Associated sources




Please enter your comment!
Please enter your name here

Most Popular

Recent Comments