Blyp OTLP
Install blyp-otlp after blyp-core when Blyp should forward logs into Grafana, Datadog, Honeycomb, or another OTLP-compatible backend. This preset keeps agents on the named-target model used by connectors.otlp.
When to install it
- the repo configures one or more OTLP connectors
- manual OTLP logging is needed
- browser or Expo code requests a named OTLP target through Blyp
What it covers
connectors.otlpas a named array- auto vs manual mode
- required target names for manual APIs
- explicit OTLP connector names in client or Expo requests
Download raw skill file
Use the canonical source file directly if you want to copy it into an agent skill directory without copying from the rendered page.
/skills/blyp-otlp/SKILL.md| Agent | Project-local path | Global path |
|---|---|---|
| Codex | .agents/skills/blyp-otlp/SKILL.md | ~/.agents/skills/blyp-otlp/SKILL.md |
| OpenCode | .opencode/skills/blyp-otlp/SKILL.md | ~/.config/opencode/skills/blyp-otlp/SKILL.md |
| Claude Code | .claude/skills/blyp-otlp/SKILL.md | ~/.claude/skills/blyp-otlp/SKILL.md |
Related docs
Canonical skill source
Copy the exact markdown file contents and drop them into your agent skill directory.
---
name: blyp-otlp
description: Portable Blyp connector add-on skill for named OTLP targets using connectors.otlp, explicit target names, auto or manual delivery modes, and client or Expo forwarding requests through Blyp.
---
# Blyp OTLP
## What this skill is for
Use this add-on when Blyp forwards logs to Grafana Cloud, Datadog, Honeycomb, or another OTLP-compatible target.
## When to use it
- Configuring `connectors.otlp`
- Managing multiple named OTLP targets
- Choosing `mode: "auto"` or `mode: "manual"`
- Supporting browser or Expo requests that target a named OTLP connector
## Blyp-specific rules and constraints
- Install `blyp-core` first.
- Configure OTLP as an array under `connectors.otlp`.
- Every OTLP target must have a unique `name`.
- Supported delivery modes are `auto` and `manual`.
- Manual OTLP APIs and client or Expo forwarding requests must target an explicit connector name.
- Browser and Expo OTLP requests still go through Blyp ingestion first.
## Required implementation steps
1. Add or update the `connectors.otlp` array in `blyp.config.*`.
2. For each target, set `name`, `enabled`, `mode`, and `endpoint`.
3. Add `auth`, `headers`, or `serviceName` if required by the backend.
4. If manual control is required, import from `@blyp/core/otlp` and pass the target `name`.
5. If browser or Expo code requests OTLP forwarding, use `{ type: "otlp", name: "<target>" }` and verify the named server connector exists.
## Verification checklist
- `connectors.otlp` is an array
- Each OTLP target has a stable `name`
- The chosen mode is explicit for each target
- Manual or client forwarding paths always include a connector name
- Browser or Expo forwarding still targets Blyp ingestion first
## References
- Config key: `connectors.otlp`
- Manual import path: `@blyp/core/otlp`
- Manual APIs: `createOtlpLogger()`, `createStructuredOtlpLogger()`