The missing OTel data source

Synthetic intelligence that speaks OTel nativelyAnd enriches every tool in your stack

Every check emits a rich OTLP insight pack — anomaly deviations in σ, dependency attribution, cross-monitor correlation signals, screenshot URLs, and W3C traceparent headers. Not metrics bolted onto a silo. Structured intelligence that flows into your existing backend.

Start FreeRead Docs
otlp span → your backend
# synthetics.check.run
synthetics.check.name     "Checkout Flow"
synthetics.anomaly.detected    true
synthetics.anomaly.metric      browser_lcp
synthetics.anomaly.deviation   +2.8σ from 14-day baseline
synthetics.third_party.domain  cdn.tagmanager.net
synthetics.third_party.bytes   847293
synthetics.correlation.checks  4 monitors affected
trace_id  4bf92f3577b34da6a3ce929d0e0e4736
screenshot https://r2.yorkermonitoring.com/...

How it works

01

Check runs from a global location

Your HTTP or browser check executes from one of 14 hosted locations — or a private location behind your firewall. Real browser, real network, real TLS handshake.

02

Anomaly scores and attribution computed

Anomaly deviations calculated against per-metric, per-location, per-hour-of-day baselines. Third-party domains classified. Cross-monitor correlation signals detected.

03

Full OTLP insight pack emitted

Metrics, traces, and logs emitted in parallel to your backend — with anomaly scores, dependency attribution, correlation signals, screenshot URLs, and W3C traceparent already computed.

What's in every insight pack

Every check run — HTTP or browser — emits the same six categories of structured intelligence into your OTel backend. No configuration required.

  • Anomaly scores
    Deviation in σ from a 14-day rolling baseline, calculated per metric, per location, and per hour of day.
  • Dependency attribution
    Third-party domains classified, payload bytes tracked, latency measured — and compared across your monitor portfolio.
  • Cross-monitor correlation
    How many other monitors share a failing pattern right now. Surfaces shared dependency failures before you correlate them manually.
  • Screenshot URLs in spans
    Screenshot stored in R2, URL embedded directly in the OTel span. Pull up visual evidence from inside Grafana, your runbook, or a PagerDuty alert.
  • W3C trace propagation
    traceparent injected into browser check HTTP requests. Your backend picks it up — synthetic check and backend trace become one distributed trace.
  • TLS context
    Certificate expiry, issuer chain, fingerprint, and TLS handshake duration emitted as span attributes on every HTTPS check.
Emitted on every check run
synthetics.anomaly.deviation+2.8σ
synthetics.anomaly.metricbrowser_lcp
synthetics.third_party.domaincdn.tagmanager.net
synthetics.third_party.bytes847293
synthetics.correlation.checks4
synthetics.tls.expiry_days42
synthetics.screenshot.urlhttps://r2.yrkr.io/...
traceparent00-4bf92f35...-01
ClickStack
First-class
Dash0
OTLP/HTTP
Grafana Cloud
OTLP/gRPC
Datadog
OTLP ingest
Honeycomb
OTLP/HTTP
Any OTLP endpoint
Standard spec

Works with your existing stack

Yorker emits standard OTLP signals. No proprietary format, no vendor lock-in. Configure your OTLP endpoint once — synthetic intelligence lands alongside your infrastructure telemetry, in the same backend, in the same dashboards.

First-class integration with the ClickStack ecosystem — ClickHouse + HyperDX. Connect any OTLP-compatible backend in under a minute.

Trace propagation

W3C traceparent injected into every browser check HTTP request. Your backend instruments pick it up — the synthetic check and the backend trace become one distributed trace in your observability backend.

No separate synthetic trace tree. No context-switching. One trace, from the Playwright browser to the database query — with the synthetic check as the root span.

w3c trace propagation
# Browser check emits root span
trace_id  4bf92f3577b34da6a3ce929d0e0e4736
span_id   a3ce929d0e0e4736
service  synthetics.browser

# Request to your API carries traceparent
traceparent 00-4bf92f35...-a3ce929d-01

# Your backend continues the trace
trace_id  4bf92f3577b34da6a3ce929d0e0e4736
parent_id a3ce929d0e0e4736
service  your-api-service

Unlike basic OTel bolt-ons

  • Checkly and Datadog Synthetics emit basic metrics to OTel. Yorker emits pre-correlated insight packs — anomaly scores, dependency attribution, and correlation signals already computed in the span before it reaches your backend.

  • No separate dashboard to context-switch to. Your synthetic intelligence lands in the same backend as your infrastructure telemetry — queryable alongside APM, logs, and infrastructure metrics.

  • W3C traceparent propagation links synthetic checks into your existing distributed traces, not a separate trace tree. One trace from browser to database.

Related Features

Browser Monitoring

Playwright checks with third-party dependency attribution and filmstrip evidence.

Learn more
Alerting

Multi-location correlation and alert triage with full OTel context.

Learn more
Private Locations

The same OTel intelligence layer running behind your firewall, at 50% off.

Learn more

Close your observability blind spot

Free tier includes 10,000 HTTP checks and 1,500 browser checks per month. No credit card required.

Start FreeRead Docs
npx yorker init