Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@ the same `gen_ai.*` span model.
Every model call goes through OpenRouter. Each demo is a self-contained npm
project — there is no workspace root.

## Mistral Example

[`mistral-support/`](mistral-support/) is a TypeScript terminal support agent
that uses Sentry's native Mistral integration. It calls Mistral directly and
includes its own setup instructions. The SDK examples use Sentry `11.0.0-rc.0`.

## What the three have in common

- `gen_ai.conversation.id` is the conversation key on all three signals in
Expand Down
6 changes: 3 additions & 3 deletions github-harness-flue/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,8 @@ while the issues it reasons about live in the app's project (`SENTRY_APP_PROJECT
All model calls route through OpenRouter (Flue's built-in `openrouter/…` provider — the only
credential needed is `OPENROUTER_API_KEY`). Sentry is wired via Flue's official integration
(`src/sentry.ts`, described under [The Sentry bridge](#the-sentry-bridge) below):
`Sentry.init` owns the global OpenTelemetry tracer provider and Flue's OTel GenAI adapter emits
the spans. Because `flue run` never loads `app.ts`, the agent module imports `src/sentry.ts`
`Sentry.init` uses `enableOpenTelemetrySetup: true` to own the global OpenTelemetry tracer
provider, and Flue's OTel GenAI adapter emits the spans. Because `flue run` never loads `app.ts`, the agent module imports `src/sentry.ts`
itself. The CLI disposes instrumentation on exit, so the bridge can flush.

```
Expand Down Expand Up @@ -139,7 +139,7 @@ sensitive key names is a denylist, and frame locals are not filtered at all. Sup
calls at all. Read it as a baseline: everything a Flue agent needs to be observable end to end,
and nothing past that.

- **Traces.** `Sentry.init` owns the global OpenTelemetry tracer provider, so Flue's
- **Traces.** `Sentry.init` uses `enableOpenTelemetrySetup: true` to own the global OpenTelemetry tracer provider, so Flue's
`@flue/opentelemetry` adapter needs no exporter of its own. Sentry's provider integrations —
the ones that patch the Anthropic, OpenAI or Vercel AI SDKs directly — are filtered out,
because the adapter already emits one `chat` span per model turn and both would count it.
Expand Down
Loading
Loading