Loading…

Skip to content

Product
Demo
Services
Docs
Pricing
Enterprise

Log inBook a demo

Join Private Beta

Documentation

Browse documentation

Start

Getting Started
ChangelogRoadmap
RoadmapRoadmap

Observability

Monitoring
Browser Monitoring
Logs
Tracing
Deployments
Services
OpenTelemetry

Operations

Incidents
Status Pages
AI Ops
Integrations

Developers

API
SDKs
CLIRoadmap

Enterprise

Enterprise
SSO
SCIM
MFA
Audit Log
Security

Start

Getting Started
ChangelogRoadmap
RoadmapRoadmap

Observability

Monitoring
Browser Monitoring
Logs
Tracing
Deployments
Services
OpenTelemetry

Operations

Incidents
Status Pages
AI Ops
Integrations

Developers

API
SDKs
CLIRoadmap

Enterprise

Enterprise
SSO
SCIM
MFA
Audit Log
Security

Documentation

OpenTelemetry

Prefer standard OTLP HTTP for traces. Mydle stores what your collectors send — no synthetic spans.

Traces Related signals Limitations

Traces

Point your OTLP HTTP exporter at /api/traces/v1/otlp with the workspace tracing token. Full product guide: Tracing.

Related signals

Logs and browser RUM use Mydle ingest endpoints (not full OTLP logs / metrics pipelines yet). Correlate via trace / session identifiers when present.

Limitations

OTLP metrics / logs pipelines are not a first-class surface.
Tracing entitlement is Pro+.

Reliability operations, connected. Observed telemetry, evidence-bound AI, and no fabricated metrics.

Sales: hello@mydle.app
Support: support@mydle.app
Account: Log in to workspace

Platform

Product overview
Service catalog
Why Mydle
Enterprise identity
Pricing

Product

Monitoring
Browser monitoring
Logs
Tracing
Deployments
Incidents
Status pages
AI Ops

Developers

Documentation
OpenAPI / Swagger
Blog
RSS

Company

Interactive demo
Private beta
Book a live demo
Contact & support
Trust center
Security
Status
Pricing

Legal

Privacy Policy
Terms of Service
Cookie Policy
Security
Data Processing
Acceptable Use
Responsible disclosure

© 2026 Mydle. All rights reserved.

Private beta · Observed data only · Engineering-first