Identity-Native Telemetry Mapping
Lookout is the platform's analytics surface. What makes it different from a generic dashboard tool is identity-nativeness: every event Lookout ingests is already stamped with the Gate-verified subject identity (per the Kibo audit ledger integration with Gate). You do not have to join an event log against a separate identity-source-of-truth — the identity is part of the event.
This tutorial walks through composing a dashboard that surfaces operational metrics broken down by user persona, geographic region, and time of day — all without writing SQL or configuring a separate data pipeline.
Prerequisites
- A Pathmaker-role account on the project
- Lookout installed (it's a Trailblazer-class extension, available in most plans)
- Some operational traffic in your project (otherwise there's nothing to chart)
Step 1 — Create a new dashboard
In the Console, navigate to Lookout → Dashboards → New. Give it a name (operational-pulse) and a description. Lookout opens a blank canvas with a widget palette on the right.
Step 2 — Add a "Calls by persona" widget
Drag a Time series widget onto the canvas. In the widget configuration:
- Metric:
count(events) - Filter:
event_type IN ("data.read", "data.write") - Group by:
subject.attributes.persona— Lookout autocompletes from your project's declared subject attributes - Time bucket: 5 minutes
- Range: last 24 hours
Save. The widget renders a stacked time-series of call volume, broken down by the user personas your IdP declares on the JWT. No join — the subject.attributes.persona is on every event because Gate put it there at session issuance.
Step 3 — Add a "Geographic distribution" widget
Drag a Map widget. Configure:
- Metric:
count(events) - Filter:
event_type = "auth.session.issued" - Group by:
subject.geo.country_code - Map style: choropleth (intensity by country)
- Range: last 7 days
Lookout renders a world map shaded by login origin. The subject.geo.country_code is established at Gate's ingress check (per the Residency Node tutorial) and propagates through every event in the session.
Step 4 — Add an "Approval queue depth" widget
Drag a Gauge widget. Configure:
- Metric:
gauge(maker_checker.queue_depth)— Lookout has prebuilt metrics for the platform's approval graphs - Group by:
queue.role - Refresh rate: 30 seconds
- Alert threshold: red above 20, amber above 10
The gauge shows live queue depth per approver role. If the Finance Approver queue spikes above 20, the gauge turns red and (if you configure alerting) sends a notification to the on-call channel.
Step 5 — Add a "Persona × geography heatmap"
Drag a Heatmap widget. Configure:
- Metric:
count(events) - X axis:
subject.geo.country_code - Y axis:
subject.attributes.persona - Range: last 24 hours
The heatmap intersects two dimensions. You see at a glance "support agents in Germany have higher call volume than support agents in the US" or "compliance officers in the UK are most active 13:00–16:00 GMT." The data was already labelled by Gate; Lookout just renders the cross-tabulation.
If you tried to produce this in a generic dashboard tool, you would:
- Export the event log to a data warehouse
- Export the identity attributes from your IdP
- Schedule a join job to associate them
- Build the visualisation against the join output
- Maintain the pipeline as either side evolves
In Lookout, you drag two fields onto a heatmap. The pipeline is already there because the identity is part of the event.
Step 6 — Add an "MFA fresh-claim correlation"
Drag a Bar chart widget. Configure:
- Metric:
count(events) - Filter:
operation IN ("data.read.field.revealed", "irreversible_action_gate.executed") - Group by:
subject.mfa_state - Range: last 24 hours
The chart shows sensitive operations split by MFA state (verified / unverified). A non-trivial bar in the unverified column for irreversible_action_gate.executed would be a misconfiguration alarm — those operations should always require fresh MFA per the gate policy. The dashboard surfaces the policy-vs-reality reality immediately.
Step 7 — Configure widget permissions
By default, dashboards inherit the dashboard creator's role. For a Pathmaker-authored dashboard intended for Scout consumption, set the access policy explicitly:
access:
view: [scout, pathmaker, warden]
edit: [pathmaker, warden]
Lookout also respects per-field privacy: even if a Scout role can view the dashboard, the underlying data must be visible to that role per the Unified Policy. Widgets aggregating fields the role cannot read render either as anonymised (counts only) or as redacted, depending on the field's analytical_visibility declaration.
Step 8 — Save and share
Click Save. The dashboard is now available at /lookout/dashboards/operational-pulse. Share the URL with the Scout role; their visit produces a paged-load dashboard that refreshes per the configured cadence.
Step 9 — Embed in the Console home page (optional)
Pathmakers can elect to surface dashboards on the Console's home page for specific role pools. Open Console settings → Home page widgets → Add. Select the dashboard and the audience role pool (scout). Scout-role users see the dashboard at sign-in.
This is the operational pulse view — the role-tailored picture of the system's state, surfaced as the first thing Scouts see when they arrive.
What just happened
You built an operational dashboard cross-tabulating events by user persona, geography, MFA state, and approval-queue role — without writing SQL, without configuring a separate identity pipeline, without operating a data warehouse. The identity-native event stream made every dimension a drag-and-drop concern.
The widgets share a common substrate (the Kibo audit ledger + the platform's identity context), which means consistency across dashboards is structural, not a process. A second dashboard composed by a different Pathmaker against the same data sees the same identity labels because they're the same upstream identity-context events.
Next
- Privacy-First Analytical Data Masking — configure analytical views that auto-redact PII per the Warden's policy.
- Designing Jurisdictional Ingress Routes — the source of the
subject.geo.country_codefield used in the map widget. - Authoring Operational Maker-Checker Approvals — the source of the approval-queue metrics used in the gauge widget.