All Collections
How does the visual ticket description variation work?
How does the visual ticket description variation work?

Learn more about the visual ticket description feature

Updated over a week ago

Baresquare tickets contain a textual description that illustrates the "what", "where", "why" and "what else" in the anomalies of your data; this forms the summarization of the reported anomaly in plain, natural language.

A visual summarization, on top of the textual one, is also available; the same information is included in both variations and switching between the two is super easy.

Textual description (default view):

Visual description (alternative view):

The "What" section in the visual description contains the key metric comparison against the expected values and the 'impact' index.

The "Where" section refers to the "address" of the reported anomaly, focusing on the two primary dimensions ('devices' and 'channel' in the example snapshot above). Whenever the anomaly is spotted on a total level, users can check the main drivers by mousing over and checking the tooltip that appears. Otherwise, the specific primary dimension values will be already visible in this section.

The "Why" section shows the contribution analysis results, i.e., which are the secondary dimension values that drove the change in the reported KPI and the identified segment (i.e., the "where") of the anomaly.

The "What else" section shows how other metrics, that have been detected by our algorithm as related to the key metric based on historical data, behaved at the same time. This only covers the system-defined related metrics and not the user-defined ones (learn more about related metrics).

Switch between the two variations:

Users can switch between the two variations (whenever both are available) by clicking on either the left/right arrows or the "carousel-indicators" (the two dots below the ticket description). When the information for displaying both is missing*, users are only able to view the default (textual) ticket description, and the navigation buttons are not visible at all.

* technical note: depends on the "leader_dimensions" key in the JSON payload of the ticket

Did this answer your question?