Skip to content
molesignal
Integrations

Plug in the stack you already run.

OpenTelemetry is the native path, while compatibility receivers make migration practical for existing agents, collectors, cloud drains, storage, and incident channels.

Self-host free Explore the product
OTLP gRPC
OTLP HTTP
OTLP Profiles
pprof upload
Pyroscope-compatible ingest
Prometheus remote_write
Elasticsearch _bulk
Loki push
Syslog UDP/TCP
Native HTTP JSON
AWS Kinesis Firehose
Cloudflare Logpush
ingest protocols
10
object-store targets
4
notification paths
10+
profiling ingest paths
3

Compatibility backed by concrete endpoints.

The catalog stays intentionally factual: each item below maps to a current receiver, storage adapter, or notification path.

Telemetry ingest

Native and compatibility paths into the shared write pipeline.

  • OTLP gRPC
  • OTLP HTTP
  • OTLP Profiles
  • pprof upload
  • Pyroscope-compatible ingest
  • Prometheus remote_write
  • Elasticsearch _bulk
  • Loki push
  • Syslog UDP/TCP
  • Native HTTP JSON

Cloud log sources

Direct receiver paths for common managed delivery services.

  • AWS Kinesis Firehose
  • Cloudflare Logpush
  • Heroku Log Drain
  • Vector
  • Fluent Bit
  • OpenTelemetry Collector

Storage

Durable columnar telemetry on the infrastructure you control.

  • Amazon S3
  • Google Cloud Storage
  • Azure Blob Storage
  • MinIO
  • Postgres metadata

Alert destinations

Route incidents into the collaboration and paging tools already in use.

  • Slack
  • Email
  • Generic webhooks
  • PagerDuty
  • OpsGenie
  • Microsoft Teams
  • Lark / Feishu
  • WeCom
  • DingTalk

migration

Migrate without a flag day.

Compatibility receivers allow a measured side-by-side evaluation before any current backend is retired.

  1. 101 · Connect

    Mirror one signal

    Use the current collector or agent and add the corresponding molesignal endpoint.

  2. 202 · Compare

    Validate fields and queries

    Confirm schema, timestamps, labels, retention, and the operator queries that matter.

  3. 303 · Correlate

    Add the next signal

    Test the cross-signal path with real service metadata and trace IDs.

  4. 404 · Cut over

    Retire a backend when ready

    Move alerts and dashboards after the replacement path has been exercised.

proof / shipped

Compatibility backed by concrete endpoints.

The catalog stays intentionally factual: each item below maps to a current receiver, storage adapter, or notification path.

  • Telemetry ingest · 10
  • Cloud log sources · 6
  • Storage · 5
  • Alert destinations · 9
Integrations

Start with the collector you already have.

The quick-start guide includes the local sandbox; the public repository documents integration examples and endpoints.

Self-host free Read the architecture