Features

One place for every signal.

otelnew correlates logs, metrics, and traces, and collects browser RUM through a first-party proxy. Instrument with OpenTelemetry and keep the data portable.

01

Logs

Structured logs stay attached to the request that produced them, so an error line opens the trace instead of a separate search.

02

Metrics

Latency, error rate, and throughput sit next to the spans they describe. Golden signals are a starting point, not a separate product.

03

Traces

Follow a request from the edge through services and datastores. The slow span is visible without stitching tools together.

04

Browser RUM

Page views, web vitals, resources, clicks, network calls, and handled errors leave the browser through rum.otelnew.com.

How a visit is recorded

Different events, one session.

Every page sends a page-view log. The dashboard adds timings and custom measurements. The errors page reports handled exceptions. The network page issues real fetches the SDK records as network requests.

Clicks on buttons and links are user-interaction events. Web vitals and resource timings are collected on each navigation.

  1. log Page view, warnings, and investigation notes
  2. error Handled exceptions from the errors page
  3. network-request Fetches to public APIs
  4. user-interaction Clicks in the nav and dashboard
  5. web-vitals LCP, INP, and CLS on each page

Try the console with sample data.

The dashboard, errors page, and network page are live on this site.

Open the dashboard