Connectors
Connectors let Blyp forward logs beyond the local console, files, or request logger pipeline.
Blyp ships first-party connector support for:
Runtime model
The connector model differs by runtime:
| Runtime | How it forwards |
|---|---|
| Server adapters and standalone loggers | direct connector delivery from the Node/Bun runtime |
| Browser client | sends to Blyp ingestion first, then the server forwards when configured |
| Expo | sends to Blyp ingestion first, then the server forwards when configured |
| Workers | not covered by PostHog error tracking |
Auto vs manual
Each server-side connector supports two modes:
mode: "auto"forwards regular Blyp server logs automaticallymode: "manual"disables automatic forwarding so you can use dedicated connector APIs directly
The dedicated helper entry points are:
@blyp/core/betterstack@blyp/core/posthog@blyp/core/sentry@blyp/core/otlp
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 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:
blyp.config.tsblyp.config.mtsblyp.config.ctsblyp.config.jsblyp.config.mjsblyp.config.cjsblyp.config.json