Observability should give engineers a clear view of what their systems are doing and not feel like another setup you have to wrestle with.
Our goal is to bring the TypeScript ecosystem the observability tools it’s been missing — built on the OpenTelemetry standard and designed to integrate natively with your favorite stack.
Every package has a peer dependency on @opentelemetry/api, so install it alongside:
pnpm add @api-blitz/otel-drizzle @opentelemetry/api
# or: npm install / yarn add / bun addThen in your code:
import { instrumentDrizzle } from "@api-blitz/otel-drizzle";Versions follow semver. Pin with ^1.0.0 (caret) to get patch and minor updates automatically.
Want to see what the traces actually look like before you install? Each package ships a playground that replays a realistic workload through the instrumentation and exports the resulting spans to a local Jaeger UI — no API keys, no database required. See EXAMPLES.md.
Releases go out by hand from a local checkout. Per change:
pnpm changeset # pick packages + bump type, write summaryWhen ready to ship the accumulated changesets:
pnpm version-packages # consumes changesets, bumps versions, updates CHANGELOGs
git commit -am "Version Packages"
pnpm release # runs build, then changeset publish
git push --follow-tagspnpm release uses the NPM_TOKEN in your shell (or npm login session) and publishes every package whose local version is ahead of the npm registry.
For the very first publish on a brand-new scope (nothing on the registry yet), skip the Changesets dance and just run:
pnpm build
pnpm -r publish --access publicNeed support for something? Open an issue to request or ship a new integration.
Originally forked from Kubiks. Continued under the @api-blitz/* scope.
This project is licensed under the MIT License.