Observe SDKs
1 min read
Observe SDKs
Tracker scripts
<!-- Analytics -->
<script defer src="https://your-observe.com/t/observe.js"
data-site-id="YOUR_SITE_ID"></script>
<!-- Error tracking -->
<script defer src="https://your-observe.com/t/observe-errors.js"
data-site-id="YOUR_SITE_ID"></script>
<!-- Session replay (structural keyframes) -->
<script defer src="https://your-observe.com/t/observe-replay.js"
data-site-id="YOUR_SITE_ID"></script>
<!-- Session replay (delta recording via rrweb — DOM mutations captured) -->
<script defer src="https://your-observe.com/t/observe-replay-delta.js"
data-site-id="YOUR_SITE_ID"></script>
<!-- Feedback widget -->
<script defer src="https://your-observe.com/t/observe-feedback.js"
data-site-id="YOUR_SITE_ID"></script>Both replay recorders ride the same v2 batch transport; sessions are indistinguishable server-side and replay through the appropriate player automatically.
Browser API
observe.track("signup", { plan: "pro" });
observe.revenue(49.99, "USD", { product: "annual" });
observe.trackVitals();
observeErrors.captureException(error);
observeErrors.captureMessage("Something went wrong");
observeErrors.addBreadcrumb({ type: "user", category: "click", message: "Button" });Server-side SDKs
| Language | Package | Install |
|---|---|---|
| Python | teploy-observe |
pip install teploy-observe |
| Go | sdk/go |
go get github.com/useteploy/teploy-observe/sdk/go |
Both ship flag clients alongside event ingest.
Sentry-protocol ingest
Stock Sentry SDKs can point at an Observe DSN
(https://<obs_key>@host/<site_id>) for error events. Transactions,
sessions, replays, profiles and attachments are acknowledged and dropped —
the per-API compatibility tables in the repository
(docs/sdk/COMPATIBILITY.md) are the authority.
Migrating from Sentry or PostHog
Tested paths — installation, credential, first event, verification, per
SDK — and dual-write recipes are in docs/sdk/MIGRATION.md in the
repository. The rule for every recipe: run both integrations side by side,
compare, and only remove the old one after the Observe data has proven
itself.