MoleSignal is under active development and is not yet 1.0. Read the Changelog before upgrading, and open an issue when behavior differs from this documentation.
Get started
Quickstart
Run MoleSignal locally with Docker Compose, send a first log, and query it.
Connect data
Send telemetry from OpenTelemetry, Vector, Fluent Bit, Prometheus, and more.
Deploy
Install with Docker Compose, a binary, or Kubernetes, then follow the production checklist.
How it works
What MoleSignal covers
One data plane for four signals
Send logs, metrics, traces, and profiles through OTLP and compatible protocols, and 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 identifiers by hand.
APM and profiling
Use trace-derived performance metrics and service topology to find slow services, failing transactions, and code hotspots.
Programmable pipelines
Route, normalize, redact, enrich, and backfill data with pipelines and reusable VRL or JavaScript functions.
Detection and incident response
Run scheduled and anomaly rules connected to incidents, on-call schedules, escalations, silences, and notification channels.
Synthetic monitoring and status pages
Probe endpoints from built-in and private locations, and publish status pages for customers.
Dashboards, reports, and sharing
Turn investigations into dashboards, saved views, scheduled reports, and restricted shares.
Mole Agent and MCP
Let an AI agent collect evidence through a governed tool catalog, while approvals protect write operations.