Collect, correlate, and investigate OpenTelemetry data in one platform.

Modulis is built on OpenTelemetry — the vendor-neutral instrumentation standard.

What is OpenTelemetry?

OpenTelemetry (OTel) is an open-source, vendor-neutral standard for instrumenting applications — a common set of APIs, SDKs, and data formats for logs, metrics, and traces, maintained under the Cloud Native Computing Foundation. Instrumenting with OTel means the instrumentation itself isn't tied to any one observability vendor.

The three signal types

Logs

Structured and unstructured application log events, correlated with the trace and service that produced them.

Metrics

Counters, gauges, and histograms describing system and application performance over time.

Traces

The end-to-end path of a request across every service it touches, with span-level timing.

OTel collectors

The OpenTelemetry Collector is a vendor-agnostic proxy that receives telemetry from your instrumented services, optionally processes it (batching, filtering, sampling), and exports it to one or more backends. In a Modulis deployment, the collector runs inside your own cloud account alongside the rest of the Modulis platform, so telemetry never has to leave your environment on its way to being processed.

How Modulis receives and processes OTel data

Modulis accepts standard OTLP (OpenTelemetry Protocol) from your instrumented services or collectors, then correlates that logs/metrics/traces data with errors, session replay, and Git/deployment metadata into a single investigation — rather than treating OTel signals as three separate, disconnected datasets the way some tools do.

Kubernetes deployment

Modulis deploys inside your own cloud account on Kubernetes, which Modulis provisions and manages for you — you don't need existing Kubernetes expertise to run it. Application instrumentation with OpenTelemetry is independent of that deployment step and works whether your own services run on Kubernetes, VMs, or containers elsewhere.

Supported languages

Because Modulis is built on the OpenTelemetry standard, any language with an OTel SDK can be instrumented. Modulis also publishes dedicated setup guides for common frameworks — see Next.js, React, Node.js, Golang, Angular, Express, Gatsby.js, Hono, Rails, and Svelte.js in the Integrations directory.

Setup overview

  1. Create your Modulis account and connect your cloud provider (AWS, GCP, or Azure).
  2. Modulis deploys the managed platform, including the OTel collector, inside your cloud account.
  3. Add OpenTelemetry SDK instrumentation (or use a framework-specific guide) to your services.
  4. Telemetry flows in and Modulis begins correlating logs, metrics, and traces automatically.

Related reading

Production Debugging →Traces & Metrics →How It Works →

FAQ

Do we need to fully migrate to OpenTelemetry to use Modulis?
No. You instrument incrementally with standard OTel SDKs and collectors as you adopt Modulis — there's no requirement to convert your entire stack at once.
Does using OpenTelemetry avoid vendor lock-in?
That's the point of the standard — OTel data is vendor-neutral, so instrumentation you write isn't tied to Modulis specifically and could, in principle, be sent elsewhere.
Which languages are supported?
Any language with an OpenTelemetry SDK is supported for instrumentation, in addition to Modulis's dedicated framework guides for Next.js, React, Node.js, Golang, Angular, Express, Gatsby.js, Hono, Rails, and Svelte.js.

Instrument your stack with OpenTelemetry

Start with the Free plan or book a demo for a guided evaluation.

Start Free Book a Demo