---
title: "Connectors"
description: "Forward Blyp logs and structured events to Better Stack, PostHog, Sentry, and OTLP backends across supported runtimes."
canonical_url: "https://www.blyp.dev/docs/connectors"
markdown_url: "https://www.blyp.dev/docs/connectors.md"
last_updated: "2018-10-20"
x_farming_labs_generated_preamble: true
---

# Connectors
URL: /docs/connectors
LLM index: /llms.txt
Description: Forward Blyp logs and structured events to Better Stack, PostHog, Sentry, and OTLP backends across supported runtimes.

# Connectors

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

Blyp ships first-party connector support for:

- [Better Stack](/docs/connectors/betterstack)
- [PostHog](/docs/connectors/posthog)
- [Databuddy](/docs/connectors/databuddy)
- [Sentry](/docs/connectors/sentry)
- [OTLP](/docs/connectors/otlp)

As of `@blyp/core@0.1.22`, 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:

| 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 automatically
- `mode: "manual"` disables automatic forwarding so you can use dedicated connector APIs directly

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:

- `@blyp/core/betterstack`
- `@blyp/core/posthog`
- `@blyp/core/databuddy`
- `@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.

```ts
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:

- `blyp.config.ts`
- `blyp.config.mts`
- `blyp.config.cts`
- `blyp.config.js`
- `blyp.config.mjs`
- `blyp.config.cjs`
- `blyp.config.json`

If a connector is enabled but logs still do not arrive, or if Better Stack and PostHog credentials are failing silently, start with [Troubleshooting](/docs/troubleshooting).

## Read next

- [Better Stack](/docs/connectors/betterstack)
- [PostHog](/docs/connectors/posthog)
- [Databuddy](/docs/connectors/databuddy)
- [Sentry](/docs/connectors/sentry)
- [OTLP](/docs/connectors/otlp)
- [Configuration](/docs/configuration)
- [Troubleshooting](/docs/troubleshooting)

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.
Docs-scoped sitemap: [/docs/sitemap.md](/docs/sitemap.md).
Well-known sitemap: [/.well-known/sitemap.md](/.well-known/sitemap.md).