Blyp Docs

Connectors

Connectors let Blyp forward logs beyond the local console, files, or request logger pipeline.

Blyp ships first-party connector support for:

As of @blyp/[email protected], connector SDKs are installed as optional peers instead of being pulled in transitively by the base package. Install only the peer packages needed by the connectors you actually enable.

Runtime model

The connector model differs by runtime:

RuntimeHow it forwards
Server adapters and standalone loggersdirect connector delivery from the Node/Bun runtime
Browser clientsends to Blyp ingestion first, then the server forwards when configured
Exposends to Blyp ingestion first, then the server forwards when configured
Workersnot covered by PostHog error tracking

Auto vs manual

Each server-side connector supports two modes:

Server-side connectors can also opt into Blyp-managed durable delivery through connectors.delivery. This adds an in-memory hot buffer plus optional SQLite persistence for retryable forwarding failures without Redis or another external queue.

The dedicated helper entry points are:

Client and Expo connector requests

Browser and Expo loggers do not talk directly to Better Stack, PostHog, Sentry, or OTLP vendor SDKs. They request forwarding through Blyp ingestion instead.

import { createClientLogger } from "@blyp/core/client";

const posthogClient = createClientLogger({
  endpoint: "/inngest",
  connector: "posthog",
});

const betterStackClient = createClientLogger({
  endpoint: "/inngest",
  connector: "betterstack",
});

const databuddyClient = createClientLogger({
  endpoint: "/inngest",
  connector: "databuddy",
});

const sentryClient = createClientLogger({
  endpoint: "/inngest",
  connector: "sentry",
});

const otlpClient = createClientLogger({
  endpoint: "/inngest",
  connector: { type: "otlp", name: "grafana" },
});

Use the same connector values in @blyp/core/expo.

Config file support

Blyp now loads configuration from any of these files in your project root:

If a connector is enabled but logs still do not arrive, or if Better Stack and PostHog credentials are failing silently, start with Troubleshooting.