Darwinium dashboards turn collected events into reusable views of traffic, decisions, accounts, devices and signals. Use them to monitor a service, identify a change, and choose the events to investigate next. In Investigations, many of the same widgets summarise the events selected by your query.
This guide uses an ecommerce demonstration dataset. Board names, step names, models and risk thresholds are examples; your organisation's configuration determines which ones you see. Screenshots show the portal in use. Personal identifiers have been replaced with illustrative values.
Start with a question
| Your question | Start with |
|---|---|
| How much traffic did we receive? | Aggregate Stats or Time Series (Count) |
| Which devices used the most accounts? | Top X Distinct Count |
| When did activity increase? | Velocity of Value |
| What is the typical value of a numeric attribute? | Statistics of Value; select Quantile 0.5 for the median |
| Which signals matched, and how often? | Signal Trigger Rate |
| How do a step and its decision relate? | Attribute Flow |
| How do users move between journey steps? | Journey Network, Chord or Circular Sankey |
| What happened to automated traffic? | Bot Type widgets, followed by a decision or step breakdown |
| Which events explain a result? | Investigations, using the same node, dates and relevant filters |
Understand the structure
A space groups related boards and sets their sharing scope. A board is one of the tabs across the top of Dashboards. A panel organises cards using a layout; panels can also contain tabs. A card displays a widget, such as Top X or Aggregate Stats.
The node selects the deployment data you are inspecting. Changing the node can change the available journeys, models, populated attributes and results. A saved configuration does not guarantee that another node collects the same attributes.