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 are cut by CI (.github/workflows/release.yml) with npm Trusted Publishing. No npm token or PAT is stored anywhere. Per change:
pnpm changeset # pick packages + bump type, write summaryCommit the changeset with your PR. Once it lands on main, the workflow type-checks and unit-tests the tree, then opens (or updates) a Version Packages PR. Merging that PR publishes every package whose version is ahead of npm, with provenance, and creates the GitHub releases and tags.
Those checks run inside release.yml rather than on the Version Packages PR itself: the PR is opened by the built-in GITHUB_TOKEN, and GitHub does not start workflow runs for events that token creates, so pull_request workflows never fire for it. Gating version and publish on a verify job keeps the release path covered without storing a PAT.
Each package must have a trusted publisher on npm pointing at this workflow (repo api-blitz/otel, workflow release.yml, environment npm). With npm >= 11.15 (older CLIs get a bare 400 because they don't send the now-required --allow-publish permission; pin the version, since npx npm@11 reuses an older installed 11.x):
npx [email protected] trust github @api-blitz/otel-<name> --repo api-blitz/otel --file release.yml --env npm --allow-publishA package can only have one trusted publisher, so npx [email protected] trust revoke <pkg> --id=<id> an existing one (see npm trust list <pkg>) before replacing it.
A brand-new package has to exist on npm before a trusted publisher can be attached, so its very first version goes out by hand from a logged-in checkout (pnpm build && pnpm --filter @api-blitz/otel-<name> publish --access public). After that, run the npm trust command above.
Need 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.