[01]
YOUR SERVICE
OpenTelemetry SDK Python / Node / Go / .NET / Java / Rust [01]
OTLP / live
free plan / 1 gb-mo
telemtra.io
// telemetry that ships Every signal.
Every signal.
One workspace.
Logs, traces, and metrics over OTLP - searched, charted, alerted, and cleaned at ingest.
Ten product surfaces. One workspace. No proprietary SDK.
accepting OTLP signals at
ingest.telemtra.io // data flow
From your service to your workspace, in four hops.
No proprietary agent. No SDK rewrite. The OpenTelemetry standard does the wire format, and Telemtra provides the hosted observability backend.
[02]
OTLP
HTTP or gRPC Standard wire format, no proprietary SDK [03]
INGEST + SHAPE
ingest.telemtra.io Data Shaper rules drop, mask, normalize before storage [04]
YOUR WORKSPACE
app.telemtra.io logs · traces · metrics · alerts · dashboards · reports // onboarding
From signup to first span, in three steps.
What the first 60 seconds actually look like - workspace, API key, and a real trace with attributes.
-
- API KEYSNAME ProductionPREFIX tk_live_h65V8X9z ACTIVECREATED 2026-06-03 11:42 UTCUSAGE curl -H "x-api-key: tk_live_h65V8X9z..."
- POST Services/pageablePOST /services/pageable 94.5msServicePlus 7.6msServicePlus 48.2msServicePlus 30.2mshttp.method POST http.status 200 service helpdesk-api
// what you get
Eight surfaces. One workspace.
The five workflows that turn telemetry into decisions, plus the three signal types they run on. Click any tile to read the moment of pain it solves.
[01] →
Dashboards
Mission control. Metric, log, trace, and note widgets on one canvas. PIN-shared with customers, scoped per service.
[02] →
Service Map
Architecture drawn from real traces. Every node and edge live, with latency and error rate per call.
[03] →
Alerts
Threshold any log field, metric, or trace latency. Email + signed webhook with full delivery audit log.
[04] →
Data Shaper
Drop, mask, or rewrite logs at ingest. No Collector edit, no server redeploy, rule applies to the next event.
[05] →
Reports & Saved Views
Save the question once, answer it any time. Pick columns, lock the date range, export to CSV.
[06] →
Logs
Structured search by service, severity, host. Detail inspector keeps every attribute the SDK sent.
[07] →
Traces
Span waterfall, status and duration per span, p95/p99 latency per operation.
[08] →
Metrics
Gauges, sums, histograms with p50-p99 modes. Attribute grouping and one-click alert creation.
// service map
Your architecture, drawn from real traffic.
Every node and edge comes from your OTLP traces - request rate, latency, and errors on each call. Here is a live one, with the error edge lit up.
// service map Live dependencies
Healthy Error
checkout-api → inventory-api · 2 errors // live
Send your first span. Watch it land.
No fake mockup. The endpoint is real, the response shape is what you get back. Paste, ship, see.
Real OTLP. Real endpoint. See the full quickstart →
// product
See your signals in real product UI.
Not concept art. Screenshots from the running app - the trace waterfall, log detail, and metric chart you will actually use.
// frequently asked
Questions worth a real answer.
OTLP, signal coverage, pricing, and where your data lives.
Is Telemtra really OpenTelemetry-native?
Yes. Telemtra ingests OTLP over HTTP and gRPC for logs, traces, and metrics. There is no proprietary SDK and no vendor-specific instrumentation - you keep your OpenTelemetry SDK or Collector setup and just point it at our endpoint.
Do I need to install a Telemtra agent or SDK?
No. Use the official OpenTelemetry SDKs and the OpenTelemetry Collector. Telemtra is the backend that receives your OTLP data, so anything that already speaks OTLP works without changes.
What telemetry signals does Telemtra support?
Logs, traces, and metrics, plus derived views like service maps, dashboards, and alerts. Histograms, counters, gauges, log severity fields, span status, and resource attributes are all preserved.
How long does setup take?
Under 60 seconds for a first span. Sign up, copy an API key, set OTEL_EXPORTER_OTLP_ENDPOINT and OTEL_EXPORTER_OTLP_HEADERS in your service or Collector, and your data appears in the workspace.
Is there a free plan?
Yes. The Free plan includes 1 GB ingest per month, 7 day retention, 3 services, and 3 alert rules. It is enough for small projects and first telemetry checks.
Where is my telemetry data stored?
Telemtra stores ingested telemetry in a hosted ClickHouse-backed store. Workspaces are isolated per tenant, and Data Shaper lets you drop or mask sensitive fields before storage.
// the rest is just plumbing Start with OpenTelemetry.
Start with OpenTelemetry.
Stay with useful workflows.
Workspace in 30 seconds. API key in one click. First span in less than two.