Skip to main content
Cross-signal correlation is MoleSignal’s defining feature. Because a trace, its logs, and the host’s metric for the same minute share the same storage, the same time index, and the same tenant scope, MoleSignal can join across them server-side — no “copy this trace_id, switch tab, paste, hope the clocks agree.”

​
The correlation API

GET /api/v1/web/correlation/{from_kind}/{to_kind}
Authorization: Bearer <jwt>
Given a starting signal (from_kind) and a target signal (to_kind), the endpoint returns the related signals with prefilled filters — the join across signals is done for you, scoped to your org and time window.

​
What you can build with it

  • 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 metric → trace → log → host and back, pushing frames as you go so you never lose context.
EndpointPurpose
GET /api/v1/web/correlation/{from_kind}/{to_kind}Server-side join across signals with prefilled filters
GET /api/v1/web/trace/{trace_id}Full trace with its spans
GET /api/v1/web/topologyService topology view
GET /api/v1/traces/service_graphService graph + RED metrics from traces
POST /api/v1/web/investigation/blobPersist an investigation stack

​
The investigation stack in the UI

The web shell turns correlation into a workflow:
  • ⌘K command palette — every stream, dashboard, alert, and saved view is one keystroke away.
  • Investigation stack (up to 6 frames) — push a frame each time you drill; navigate with ⌘[ and ⌘]; pin a frame to keep its context while you explore.
  • Every clickable action is keyboard-reachable.
The correlation API spec is complete; web integration is in progress. Track the current state in the project status.