Current view: XpoLog V7 (Latest). Available: XpoLog V6 and XpoLog V5

Skip to end of metadata
Go to start of metadata

The Venn diagram is a diagram that shows possible logical relations between a finite collection of different sets. These diagrams depict elements as points in the plane, and sets as regions inside closed curves.

To add a Venn diagram Gadget:

  1. In Title, type a name for the gadget.
  2. In Search Query, enter a search query that uses count and group by two items - the first item will be used for the calculation and the display will be by the second item. You may test your search in the search console prior to defining the venn.
  3. In Time Range, select the time frame following which the gadget display is to be refreshed.
  4. More Settings:
    1. GROUP LABEL
      1. Show/Hide - displays the grouped by item names or hides them on the venn itself.
      2. Show only ID Numbers - display numeric IDs instead of names which may be long depends on the grouped by items.
    2. INTERSECTION (OF GROUPS) LABELS

      1. Show/Hide intersection labels - displays the grouped by items names or hide them in the intersections.
      2. Show only ID Numbers - display numeric IDs instead of names which may be long depends on the grouped by items in the intersections.
      3. Show Number of groups per intersection - shows how many groups are part of an intersection.
    3. LEGEND - controls the legend display below the venn.
    4. DATA PRIORITY - controls whether to give a higher priority to the number of participants per intersection or to the count result (volume) or the group by.
  5. Click the Save button.

  6. The gadget is saved in the dashboard.

Exampleerrors in an environment -  the following sankey shows number of errors found in logs in a flow diagram: SOURCE LOG >> APPTAG >> SOURCE SERVER (using the query: error | count | group by ext.log,ext.app, ext.server | order by count desc) where specific flows are highlighted in red and others in orange



Example: The following venn shows the relationship total number of actions per user in a system, the query behind it is - * in log.system audit | count | group by user,action type --> for each user, the query calculates how many actions there were from each type and combine them into sets. You can understand from the venn that most users performed either end/start process or change.


 

  • No labels