flow_debugger

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
flow_debugger [2016/07/21 08:17]
admin [Subsections]
flow_debugger [2016/07/21 08:25] (current)
admin
Line 24: Line 24:
 ====Diagram==== ====Diagram====
  
-{{:flow_debugger.png?​nolink|}}+{{:sankey-flowdebugger.png?​nolink|}}
  
 The flow debugger diagram should be rather intuitive. You should read the graph from left to right, as this represents the most common way in which callers are navigating through your application. Each node of the graph represents a node and the paths between the nodes represent the paths taken through the application. The size of the nodes and paths relative to one another gives a sense of scale in regards to how frequently each trouble item is occurring at that specific node, the larger nodes representing the more frequently trouble items at the node and the smaller nodes representing less frequent trouble items at the node. By default, all nodes will start with a value of 0, indicating no trouble items and will scale relative to how many trouble items occurred at a given node. The flow debugger diagram should be rather intuitive. You should read the graph from left to right, as this represents the most common way in which callers are navigating through your application. Each node of the graph represents a node and the paths between the nodes represent the paths taken through the application. The size of the nodes and paths relative to one another gives a sense of scale in regards to how frequently each trouble item is occurring at that specific node, the larger nodes representing the more frequently trouble items at the node and the smaller nodes representing less frequent trouble items at the node. By default, all nodes will start with a value of 0, indicating no trouble items and will scale relative to how many trouble items occurred at a given node.
Line 32: Line 32:
 You can also hover over the paths between nodes to see the details of the path as well as the total number of trouble items at a given node. The image below is a sample of the help text which indicates there were 2 total nomatch events at the register_caller -> enter_phone_number form item node. You can also hover over the paths between nodes to see the details of the path as well as the total number of trouble items at a given node. The image below is a sample of the help text which indicates there were 2 total nomatch events at the register_caller -> enter_phone_number form item node.
  
-{{:flow_debugger_helptext.png?​nolink|}}+{{:tooltip2.png?​nolink|}}
  
 ===Draggable=== ===Draggable===
Line 38: Line 38:
 One unique feature of the diagrams is that the nodes themselves can be selected and dragged. You can click and drag the nodes as desired to relocate the nodes for a clearer path or to manipulate the graph as desired. Here's a simple sample of the above diagram after relocating the nodes. One unique feature of the diagrams is that the nodes themselves can be selected and dragged. You can click and drag the nodes as desired to relocate the nodes for a clearer path or to manipulate the graph as desired. Here's a simple sample of the above diagram after relocating the nodes.
  
-{{:flow_debugger_reordered.png?​nolink|}}+{{:draggable2.png?​nolink|}}
  
  
flow_debugger.txt · Last modified: 2016/07/21 08:25 by admin