dotOtel is the OpenTelemetry-powered APM that gives .NET teams logs, traces and metrics in one place. Sign up, send your first trace, and see what your application is actually doing — in under a minute.
Point your OpenTelemetry exporter and you'll see data in under a minute.
Three signals, one workspace, zero learning curve.
dotOtel speaks OpenTelemetry out of the box. If your app uses the OpenTelemetry SDK, you're already 90% there — swap an endpoint and you're sending data.
See the slow request, the trace that explains why, and the log line that confirms it — without jumping between four tabs. Everything is correlated by trace and resource.
Full-text log search, trace filtering by service, operation, duration or error, time-series charts for any metric. Find what you need without learning a new query language.
Sub-second queries on millions of spans. No throttling, no slow dashboards while you're trying to debug a live incident.
Per-tenant workspaces, role-based access, rotatable ingest tokens. Onboard your team without juggling permissions or rebuilding dashboards.
Per-record pricing in cents. No monthly minimums, no per-host fees. A quiet weekend produces a quiet invoice.
Sixty seconds, roughly.
Sign up at app.dototel.net. You get an ingest endpoint and a token immediately.
Set the endpoint on your existing OpenTelemetry exporter. No new agents, no sidecars, no library swaps.
Open the dashboard. Your services, requests and errors appear in real time — ready to search, filter and chart.
Four scenarios .NET teams hit every week — and what changes.
Before: "Checkout feels slow." You skim logs, suspect the database, add timing logs, redeploy, wait.
With dotOtel: Open the trace for POST /checkout, see the waterfall — four of six spans are EF queries, one taking 1.2s. N+1 spotted. Fix shipped before lunch.
Before: Spike in 502s wakes the on-call. Where? Why? Two hours of grepping pod logs.
With dotOtel: Filter errors in the last hour. They cluster around one pod, all timing out on a single downstream service. You know exactly which team to wake — not your code.
Before: Deploy v2.4. Wait nervously. Check error rate by refreshing a Kibana dashboard for twenty minutes.
With dotOtel: Open the metric for request volume, p95 latency, error count. All three look like yesterday. Stand-up is calm. You ship Friday at 3pm.
Before: A scheduled job used to take 8s. Now it's 14s. Nobody knows when it changed.
With dotOtel: Chart the job's duration over a month. See the exact day it stepped up. Diff the trace before/after — one extra HTTP call. Twenty-minute fix.
Every major OpenTelemetry instrumentation library works out of the box — here's what most .NET teams already have running.
Not on .NET? OpenTelemetry SDKs for Go, Python, Node, Java, Rust and Ruby all speak the same protocol — dotOtel ingests them too.
Less time hunting, more time shipping.
Spot the slow endpoint, the failing dependency, the silent retry storm — before the support ticket lands.
Click a trace, see the exact span that slowed everything down. Stop reading log files by hand.
Real numbers on every request, queue, and dependency. The kind of data that ends arguments in stand-up.
OpenTelemetry is the standard. Your instrumentation stays yours — if you ever switch tools, your spans come with you.
Your telemetry lives in EU data centers. Standard DPA, no transatlantic transfer concerns.
Real engineers behind the product, reachable when something matters. Not a chatbot that escalates after two days.
Three paths to observability in a .NET shop — the honest trade-offs.
| What matters | dotOtel | US-hosted SaaS APM | DIY OSS stack |
|---|---|---|---|
| Time to first trace | Minutes | Minutes | Days to weeks |
| EU data residency & DPA | Default (Hetzner DE) | Add-on or unavailable | You choose, you manage |
| OpenTelemetry-native ingest | Yes | Via adapters / agents | Yes |
| Logs + traces + metrics in one UI | Yes, correlated | Usually yes | Loki + Tempo + Prometheus + Grafana |
| .NET-team focus & tested integrations | Yes | Generic, language-neutral | n/a — you wire it |
| Ongoing operations cost | Pay-per-record (Stripe) | Annual contract or per-host | Infra + engineering hours |
| Minimum commitment | None — cancel from Stripe portal | Typically annual | Whatever you build |
| Support contact | Direct to engineers | Tiered support portal | Community / yourself |
| Vendor lock-in on instrumentation | None — OpenTelemetry | Often vendor SDK | None — OpenTelemetry |
None of these are wrong. Pick the column that matches what you actually need.
Three signals, three flat rates — per million ingested records. Billed monthly via Stripe.
Full-text searchable, correlated to traces by id, retained according to your account settings.
Full trace waterfalls with attributes, errors and service breakdown. The signal most teams reach for first.
Gauges, counters and histograms. Chart per metric, alert on thresholds, slice by attribute.
Metered per record, so any volume scales linearly — 10 000 000 logs is €3.50, 100 000 000 spans is €35. See the Terms for the full schedule.
If yours isn't here, mail us — we read everything.
Any OTLP-compatible exporter. For .NET that's the official
OpenTelemetry.Exporter.OpenTelemetryProtocol NuGet package.
We also accept OTLP from Go, Python, Node.js, Java, Rust, Ruby and PHP —
the protocol is the same regardless of language.
Inside the European Union, on infrastructure operated by Hetzner Online GmbH in Germany. We can sign a standard Data Processing Agreement on request before you upload production data.
Retention is configurable per workspace. Default windows are sized so most teams never need to think about it; longer retention for compliance scenarios is available on request. After account termination, your data stays available for export for 30 days, then is irreversibly deleted.
Yes — you can define rules on metrics, logs and traces, and route alerts to email or webhook (Slack, Teams, PagerDuty via a webhook URL). Per-tenant channels, no extra add-on.
Absolutely. dotOtel is OpenTelemetry-native, not .NET-only. Any service that speaks OTLP/HTTP — Go microservice, Python data pipeline, Node.js API, Java backend — sends to the same workspace. The .NET focus is about which integrations we test against and which audience we write the docs for, not a hard restriction on what you can ingest.
For regulated industries or air-gapped environments we offer on-premises deployment under a separate agreement. The hosted product at app.dototel.net is the default and where most teams start.
Pay-per-use, no monthly minimum. We meter every ingested record and
charge per 100 000: €10 for logs,
€15 for spans, €5 for metric
datapoints. Stripe issues an automatic monthly invoice to the card on
file; you can pause, update the payment method or cancel directly from
the Stripe Customer Portal. All prices in EUR, exclusive of VAT.
There is no hard cap by default — pay-per-use means the next month's bill simply reflects the spike. If you need a fixed ceiling (for example to protect against runaway log floods from a misconfigured library), set drop rules in the workspace or contact us to configure a hard ingest limit on the account.
Yes. Telemetry can be exported in standard formats (OTLP JSON, Parquet for long-form archives). After cancellation you have 30 days to pull everything out before deletion.
A workspace and your first trace in the time it takes to grab a coffee.
Open dotOtel, create a workspace, send your first trace. Self-serve, ready in minutes.
Account anlegen →Larger team, regulated environment, custom retention? Tell us what you need — we'll get back within one business day.
Prefer email?
mail@software.tirol