Skip to content

docs(observability): add Future AGI as a supported OTLP backend #2713

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

Open
SuhaniNagpal7 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(observability): add Future AGI as a supported OTLP backend #2713

Show file tree
Hide file tree
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
58 changes: 55 additions & 3 deletions docs/development/agent-integration/observability.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ graph LR
%% Destinations
Phoenix[Phoenix<br/>:6006<br/>✓ Built-in]
Langfuse[Langfuse<br/>Cloud<br/>⚙ Config Required]
FutureAGI[Future AGI<br/>Cloud<br/>⚙ Config Required]
Custom[Custom<br/>Backend<br/>⚙ Config Required]

%% Data flows
Expand All @@ -26,18 +27,23 @@ graph LR

OTLP --> Phoenix
OTLP --> Langfuse
OTLP --> FutureAGI
OTLP --> Custom

%% Simple styling
classDef default fill:#f9f9f9,stroke:#333,stroke-width:2px,color:#000
classDef collector fill:#e3f2fd,stroke:#1976d2,stroke-width:2px,color:#000
classDef builtin fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px,color:#000
classDef optional fill:#fff3e0,stroke:#f57c00,stroke-width:2px,stroke-dasharray: 5 5,color:#000
classDef langfuse fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px,stroke-dasharray: 5 5,color:#000
classDef futureagi fill:#fce4ec,stroke:#c2185b,stroke-width:2px,stroke-dasharray: 5 5,color:#000
classDef custom fill:#eeeeee,stroke:#212121,stroke-width:2px,stroke-dasharray: 5 5,color:#000


class OTLP collector
class Phoenix builtin
class Langfuse,Custom optional
class Langfuse langfuse
class FutureAGI futureagi
class Custom custom
```

For telemetry to flow successfully, it must be enabled at three levels:
Expand Down Expand Up @@ -166,7 +172,7 @@ collector:
otlphttp/langfuse:
endpoint: "https://cloud.langfuse.com/api/public/otel" # EU data region
headers:
Authorization: "Basic <auth-string>"
Authorization: "Basic <YOUR_AUTH_STRING>"
pipelines:
traces:
receivers: [ otlp ]
Expand All @@ -192,10 +198,56 @@ Check your Langfuse project dashboard for incoming traces and metrics.

</Steps>

### Enable Future AGI Observability

[Future AGI](https://futureagi.com) is an open-source e2e agent engineering and optimization platform that helps you ship self-improving AI agents. Its tracer endpoint accepts OpenTelemetry OTLP/HTTP, so you can route Agent Stack traces to it through the same collector config used for Langfuse.
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase "through the same collector config used for Langfuse" might be interpreted as using the exact same configuration file or settings. It's clearer to state that it uses a similar configuration pattern.

[Future AGI](https://futureagi.com) is an open-source e2e agent engineering and optimization platform that helps you ship self-improving AI agents. Its tracer endpoint accepts OpenTelemetry OTLP/HTTP, so you can route Agent Stack traces to it using a similar collector configuration pattern as Langfuse.


<Steps>

<Step title="Get Future AGI credentials">
1. Sign up at [app.futureagi.com](https://app.futureagi.com)
2. From your dashboard, copy your `FI_API_KEY` and `FI_SECRET_KEY`
</Step>

<Step title="Create a configuration file (config.yaml):">
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The colon at the end of the step title is inconsistent with other step titles in this file (e.g., lines 125, 136, 141, 149, 162, 207) and is generally unnecessary for a title.

<Step title="Create a configuration file (config.yaml)">

```yaml
collector:
exporters:
otlphttp/futureagi:
endpoint: "https://api.futureagi.com/tracer/v1/traces"
headers:
X-API-KEY: "<YOUR_FI_API_KEY>"
X-SECRET-KEY: "<YOUR_FI_SECRET_KEY>"
pipelines:
traces:
receivers: [ otlp ]
processors: [ memory_limiter, filter/phoenix, batch ]
exporters: [ otlphttp/futureagi ]
```
</Step>

<Step title="Start the platform with the configuration">
```bash
agentstack platform start -f config.yaml
```
</Step>

<Step title="Run and View">

Execute an agent to generate data:
```sh
agentstack run chat "Hello"
```
Open your project in the [Future AGI dashboard](https://app.futureagi.com) to inspect traces, prompts, completions, and tool execution details.
</Step>

</Steps>

## Additional Resources

- **OpenTelemetry Docs**: https://opentelemetry.io/docs/
- **Langfuse Docs**: https://langfuse.com/docs
- **Phoenix Docs**: https://docs.arize.com/phoenix
- **Future AGI Docs**: https://docs.futureagi.com
- **Prometheus Docs**: https://prometheus.io/docs/
- **Grafana Docs**: https://grafana.com/docs/
58 changes: 55 additions & 3 deletions docs/stable/agent-integration/observability.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ graph LR
%% Destinations
Phoenix[Phoenix<br/>:6006<br/>✓ Built-in]
Langfuse[Langfuse<br/>Cloud<br/>⚙ Config Required]
FutureAGI[Future AGI<br/>Cloud<br/>⚙ Config Required]
Custom[Custom<br/>Backend<br/>⚙ Config Required]

%% Data flows
Expand All @@ -26,18 +27,23 @@ graph LR

OTLP --> Phoenix
OTLP --> Langfuse
OTLP --> FutureAGI
OTLP --> Custom

%% Simple styling
classDef default fill:#f9f9f9,stroke:#333,stroke-width:2px,color:#000
classDef collector fill:#e3f2fd,stroke:#1976d2,stroke-width:2px,color:#000
classDef builtin fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px,color:#000
classDef optional fill:#fff3e0,stroke:#f57c00,stroke-width:2px,stroke-dasharray: 5 5,color:#000
classDef langfuse fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px,stroke-dasharray: 5 5,color:#000
classDef futureagi fill:#fce4ec,stroke:#c2185b,stroke-width:2px,stroke-dasharray: 5 5,color:#000
classDef custom fill:#eeeeee,stroke:#212121,stroke-width:2px,stroke-dasharray: 5 5,color:#000


class OTLP collector
class Phoenix builtin
class Langfuse,Custom optional
class Langfuse langfuse
class FutureAGI futureagi
class Custom custom
```

For telemetry to flow successfully, it must be enabled at three levels:
Expand Down Expand Up @@ -166,7 +172,7 @@ collector:
otlphttp/langfuse:
endpoint: "https://cloud.langfuse.com/api/public/otel" # EU data region
headers:
Authorization: "Basic <auth-string>"
Authorization: "Basic <YOUR_AUTH_STRING>"
pipelines:
traces:
receivers: [ otlp ]
Expand All @@ -192,10 +198,56 @@ Check your Langfuse project dashboard for incoming traces and metrics.

</Steps>

### Enable Future AGI Observability

[Future AGI](https://futureagi.com) is an open-source e2e agent engineering and optimization platform that helps you ship self-improving AI agents. Its tracer endpoint accepts OpenTelemetry OTLP/HTTP, so you can route Agent Stack traces to it through the same collector config used for Langfuse.
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase "through the same collector config used for Langfuse" might be interpreted as using the exact same configuration file or settings. It's clearer to state that it uses a similar configuration pattern.

[Future AGI](https://futureagi.com) is an open-source e2e agent engineering and optimization platform that helps you ship self-improving AI agents. Its tracer endpoint accepts OpenTelemetry OTLP/HTTP, so you can route Agent Stack traces to it using a similar collector configuration pattern as Langfuse.


<Steps>

<Step title="Get Future AGI credentials">
1. Sign up at [app.futureagi.com](https://app.futureagi.com)
2. From your dashboard, copy your `FI_API_KEY` and `FI_SECRET_KEY`
</Step>

<Step title="Create a configuration file (config.yaml):">
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The colon at the end of the step title is inconsistent with other step titles in this file (e.g., lines 125, 136, 141, 149, 162, 207) and is generally unnecessary for a title.

<Step title="Create a configuration file (config.yaml)">

```yaml
collector:
exporters:
otlphttp/futureagi:
endpoint: "https://api.futureagi.com/tracer/v1/traces"
headers:
X-API-KEY: "<YOUR_FI_API_KEY>"
X-SECRET-KEY: "<YOUR_FI_SECRET_KEY>"
pipelines:
traces:
receivers: [ otlp ]
processors: [ memory_limiter, filter/phoenix, batch ]
exporters: [ otlphttp/futureagi ]
```
</Step>

<Step title="Start the platform with the configuration">
```bash
agentstack platform start -f config.yaml
```
</Step>

<Step title="Run and View">

Execute an agent to generate data:
```sh
agentstack run chat "Hello"
```
Open your project in the [Future AGI dashboard](https://app.futureagi.com) to inspect traces, prompts, completions, and tool execution details.
</Step>

</Steps>

## Additional Resources

- **OpenTelemetry Docs**: https://opentelemetry.io/docs/
- **Langfuse Docs**: https://langfuse.com/docs
- **Phoenix Docs**: https://docs.arize.com/phoenix
- **Future AGI Docs**: https://docs.futureagi.com
- **Prometheus Docs**: https://prometheus.io/docs/
- **Grafana Docs**: https://grafana.com/docs/