--- title: "Investigations overview | Darwinium" slug: "investigations-overview" description: "Start here after Darwinium has processed an interaction." updated: 2026-10-16T10:21:57Z published: 2026-10-16T10:21:57Z canonical: "docs.darwinium.com/investigations-overview" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt > Use this file to discover all available pages before exploring further. # Investigations overview Start here after Darwinium has processed an interaction. Investigations shows recorded events and their assessment results; [Workflows](/docs/journey-lifecycle-management) is where you change the configuration that generates them. ## Find your first event 1. Select the node for the environment you tested. 2. Open **Investigations → Query** and select a time range covering the interaction. 3. Search for a known journey or step, such as `step_name = "login_submit"`, using your configured name. 4. Select **Search**, then double-click a matching row to inspect its event details. 5. Check the mapped identifiers, profiling fields and configured signals, scores or decision. Use the journey ID to follow related events. Use [Search events](/docs/query-view) for query controls, [Customize the event table](/docs/query-data-table) for columns, and [Follow a journey timeline](/docs/journey-view) for session context. If a new integration has produced no events, return to [Deployment confirmation](/docs/deployment-confirmation). The Investigations section on Portal is available to investigate and query journeys and events processed by Darwinium. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1722274213980.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A12%3A52Z&se=2026-11-23T00%3A12%3A52Z&sr=b&sp=r&sig=ZwvkKoC9ZSJNYe7eYhKP1MUMSstAZsljdGAalyo0kEw%3D) The investigations functionality is intended for searching and reviewing details about the events processed by Darwinium ## Query View See Query View. The Query view is the best place to searches and find journeys that have gone through the Darwinium risk decision engine. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1722274178557.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A12%3A52Z&se=2026-11-23T00%3A12%3A52Z&sr=b&sp=r&sig=NNDr4hhoDvsm0H2H6g204QC8Y%2FGdARl%2BMj7IEWraVhE%3D) Events are searched over using the [Darwinium Query Language](/v1/docs/query-syntax-1). That is the same language as used in rules, which ensures consistency between: 1. how you can search over events in this Investigations view 2. how you may define a binary rule to run in the Darwinium rule engine That helps to translate the outcome of an investigation search directly into a real time rule > [!NOTE] > **Q: What is the delay for seeing events in Darwinium after being processed?** > > It should only take a few seconds after an event is processed by the Darwinium real-time engine to appear in the Investigations Portal ## Event Sidebar The event sidebar can be triggered upon *double* clicking any row of data in the table. The event sidebar works best to analyse the specific details about the Darwinium event like: - What was the Darwinium decision and why - What signals and scores evaluated on the event - What was the email/device/ip/location/device forensics on this event ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image(168).png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A12%3A52Z&se=2026-11-23T00%3A12%3A52Z&sr=b&sp=r&sig=HYGOsmJCFkcQ18ViL2DZQI2dQoL5ebl%2Bo2EzYhKC0Xo%3D) > [!TIP] > Tip: Full event data > > You can also right-click a row of data -> show raw event data to see and search on the full event blob ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image(170).png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A12%3A52Z&se=2026-11-23T00%3A12%3A52Z&sr=b&sp=r&sig=XOp8MpVMb9GTVqSdvrzMJWIm0L0i9O%2BgwTB%2F3bgoERs%3D) #### Event Sidebar: Filtering Additionally, the event sidebar is a useful way of forming queries without needing to know the search syntax; Hover over *any attribute value* in the sidebar to see a menu that adjusts your Investigations Search query automatically. It will populate with the attribute name and the correct function when searching for that attribute type. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image(169).png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A12%3A52Z&se=2026-11-23T00%3A12%3A52Z&sr=b&sp=r&sig=ss6JjC%2BxVFF%2BNx%2BsRskr%2B4OTGYKS%2BCnhGlEJHlOQdFQ%3D) - Filter:Value (Add to Query): use AND to add this attribute value check to search - Replace Query (Replace Query): delete current search and replace with this attribute value check - Filter:Condition (Add to Query): If a derived attribute (like a signal), use AND to add the underlying condition to search - Filter:Condition (Replace Query): If a derived attribute (like a signal), delete current serach add replace with the underlying condition to search ## Journey View See [Journey View](/v1/docs/journey-view). Darwinium places emphasis on the continuous session that a user has with your site or mobile application. The Journey View is perfect for isolating a particular user session from start to finish. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image(167).png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A12%3A52Z&se=2026-11-23T00%3A12%3A52Z&sr=b&sp=r&sig=3etYFLAtHYkcc1TIVcmhb%2FoGVfGzwO1aeZq%2BO5pZB3M%3D) The Data Table and sidebar are present in this view too. ### Identifier View See Identifier View. The Query and Journey view are useful for the tabular data. But it can help investigations to have a view showing which identifiers and attributes are **linked.** Linked meaning, used together at least once on a customer journey processed by Darwinium. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image(171).png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A12%3A52Z&se=2026-11-23T00%3A12%3A52Z&sr=b&sp=r&sig=RTXNqeHWGnsFzdx3pHtAZcsCi9S%2BG%2FxscUu9V5trb5g%3D) Identifier view can be used to: - Search for attribute value and linked identifiers in a period of time - Search for attributes by *signature similarity* - Perform a number of hops (attributes values two or three links away from original) And even perform operations such as: - Adding [labels](/v1/docs/labels) to identifier values - Export graph data to JSON ## Investigate agent and MCP activity Once [MCP and JSON-RPC steps](/docs/monitor-mcp-jsonrpc-traffic) are deployed, use the same investigation tools to inspect tool calls, mapped arguments, response results and errors. Filter to the relevant journey and step; add mapped fields to the [event table](/docs/query-data-table). A shared journey requires consistent session correlation in the integration.