MoleSignal is under active development. Review the changelog before upgrading and
open an issue when behavior differs from this
documentation.
From telemetry intake to incident response
From OpenTelemetry intake through cross-signal investigation, real-time response, and controlled automation, every workflow shares the same organization, time, and storage context.Unified telemetry data plane
Send logs, metrics, traces, and profiles through OTLP and compatible protocols, then store them
under one organization and stream model.
Cross-signal investigation
Drill from metrics into traces, logs, hosts, and RUM sessions within one time window without
copying correlation identifiers by hand.
APM and continuous profiling
Use trace-derived performance metrics and service topology to find slow services, failing
transactions, expensive dependencies, and code hotspots.
Programmable telemetry pipelines
Route, normalize, redact, enrich, and backfill data with pipelines and reusable functions.
Real-time detection and incident response
Run scheduled, real-time, and anomaly rules connected to incidents, schedules, escalations,
silences, and subscriptions.
Dashboards, reports, and sharing
Turn investigation results into dashboards, saved views, scheduled reports, exports, and
restricted shares.
Evidence-backed AI investigation
With the Enterprise
agent entitlement, let Mole Agent collect evidence while risk levels and
approvals protect write operations.Multi-tenant governance and access control
Govern access through organization isolation, roles, service accounts, SSO, auditing, licensing,
and the protected platform scope.
Start here
- Follow the Quickstart to run a local instance and send telemetry.
- Read Core concepts for signals, streams, organizations, permissions, and storage.
- Use the User guide to learn navigation and the investigation workflow.
- Choose a production topology in Deployment and Distributed deployment.