Cross-signal correlation combines stable identifiers, an organization boundary, and a shared time
window. MoleSignal builds target filters on the server, eliminating manual copying of a trace_id,
service, host, or session id between pages.
The correlation API
Given a starting signal (from_kind) and a target signal (to_kind), the endpoint returns related
signals with prefilled filters. The server performs the cross-signal join within the active
organization and time window.
Available workflows
- Service graph + RED metrics derived from traces, ready to render as a topology view
(
GET /api/v1/traces/service_graph).
- Time anchor — one click zooms and propagates the time range across all panels.
- Investigation stack — drill
RUM → trace → log → metric → profile and back while each frame
preserves investigation context.
The investigation stack in the UI
The web shell turns correlation into a workflow:
- ⌘K command palette — opens every stream, dashboard, alert, and saved view with one keystroke.
- Investigation stack (up to 6 frames) — push a frame for each drill, navigate with
⌘[ and
⌘], and pin a frame to preserve context during exploration.
- Every clickable action is keyboard-reachable.
The stack can be serialized to a short server-side investigation blob for a shareable URL. Opening
that URL still requires normal authorization for every referenced resource. Last modified on August 4, 2026
