Skip to content

chore: refactor observability page #81

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joshua-mo-143 merged 1 commit into from
Jan 30, 2026
Merged

chore: refactor observability page #81

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 0 additions & 12 deletions pages/docs/concepts/observability.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,6 @@ In practice, this can include:

Rig focuses primarily on **structured traces and logs** via the [`tracing`](https://docs.rs/tracing) ecosystem.

---

## What observability gives you in Rig

Rig emits structured telemetry that allows you to:
Expand All @@ -34,8 +32,6 @@ Rig follows the [**OpenTelemetry GenAI Semantic Conventions**](https://opentelem
- [Arize Phoenix](https://phoenix.arize.com/)
- Other OpenTelemetry-compatible backends

---

## The easiest way to get started (recommended)

If you just want to _see what Rig is doing_, the fastest path is **Langfuse**.
Expand Down Expand Up @@ -81,8 +77,6 @@ fn init_tracing() {

Once this is set up, model calls, agent invocations, multi-turn agent loops and tool executions will automatically appear in the Langfuse UI.

---

## Agent span naming and customisation

By default, agent spans use a generic name such as `invoke_agent`.
Expand All @@ -96,8 +90,6 @@ However, Rig attaches attributes like:

You can use these attributes to rename spans **in your observability backend**.

---

## Setting up an OpenTelemetry Collector (advanced)

You only need an OpenTelemetry Collector if:
Expand Down Expand Up @@ -135,8 +127,6 @@ This configuration:
- Renames agent spans using their agent name
- Exports traces to Langfuse

---

## I don’t want spans, just logs

That’s completely fine.
Expand Down Expand Up @@ -198,8 +188,6 @@ tracing_subscriber::registry()
.init();
```

---

## Troubleshooting

- **Spans appear out of order**
Expand Down