OpenTelemetry-native observability

Observability, rebuilt for what's next.

otelnew brings your logs, metrics, and traces together in one OpenTelemetry-native platform. Instrument once, see everything, and move from alert to root cause in minutes, not hours.

  • Logs, metrics, and traces
  • Built on OpenTelemetry
  • No vendor lock-in

The platform

Traditional monitoring wasn't built for this.

Modern systems are distributed, dynamic, and noisy. Traditional monitoring tools weren't built for them.

otelnew is a next-generation observability platform designed from the ground up around OpenTelemetry, the open standard for telemetry data. It correlates logs, metrics, and traces automatically, so engineers can follow a request across services, spot anomalies in real time, and pinpoint root causes without switching between tools.

Because it's built on open standards, your instrumentation stays portable and your data stays yours. Whether you're running Kubernetes, serverless, or a hybrid cloud, otelnew gives you full-stack visibility without the complexity or the lock-in.

  • Instrument once One open standard for logs, metrics, and traces, across every service.
  • See the whole request Follow a call across services without reconstructing the path by hand.
  • Keep the data Portable instrumentation, and telemetry that isn't locked to one vendor.

Three signals, one timeline

Logs, metrics, and traces in the same place.

Stop pivoting between tools to explain a single request. otelnew keeps the symptom, the span, and the log line together.

Logs

The lines that explain a failure, already tied to the request that produced them.

Metrics

Rate, errors, and latency as they move, so an anomaly is visible while it is still happening.

Traces

The path a request took across services, including the span where time disappeared.

From alert to root cause

Minutes, not a tour of five tools.

A latency alert is a starting point. otelnew correlates the trace and the logs automatically, so the failing hop and the reason it failed are on the same timeline.

Latency checkout error rate 2.4% p95 1.84s · last 15 min
  1. edge-gateway12ms
  2. checkout-api90ms
  3. postgres1.62s

ERROR connection pool exhausted · timeout waiting for connection

Same trace. Same request. No tool switch.

How it works

One pipeline from instrumentation to answer.

  1. Instrument once

    Emit logs, metrics, and traces with OpenTelemetry. The same standard covers every service you run.

  2. Correlate automatically

    otelnew stitches those signals together, so a spike, a span, and a log line land on the same request.

  3. Resolve in minutes

    Go from the alert to the failing service and the line that explains it, without opening another product.

Where it runs

Kubernetes, serverless, or hybrid cloud.

Full-stack visibility without a second monitoring standard and without locking the instrumentation to one vendor.

Kubernetes

Services, workloads, and the requests between them on one OpenTelemetry pipeline.

Serverless

Functions and the APIs they call, visible in the same place as the rest of the system.

Hybrid cloud

Cloud and data-center services in one view, with instrumentation you can take with you.

Open standards

Your instrumentation stays yours.

otelnew is built on OpenTelemetry so the work you do to instrument a service stays portable. Your data stays yours. Switching tools later should not mean rewriting telemetry.

otelnew is an independent platform built on OpenTelemetry. It is not part of, affiliated with, or endorsed by the OpenTelemetry project.

See your systems on one timeline.

Bring logs, metrics, and traces into an OpenTelemetry-native platform.

Request access