Skip to content

docs(traces): add Future AGI to OTel-compatible visualization tools#809

Open
SuhaniNagpal7 wants to merge 1 commit intostrands-agents:mainfrom
SuhaniNagpal7:add-future-agi-traces
Open

docs(traces): add Future AGI to OTel-compatible visualization tools#809
SuhaniNagpal7 wants to merge 1 commit intostrands-agents:mainfrom
SuhaniNagpal7:add-future-agi-traces

Conversation

@SuhaniNagpal7
Copy link
Copy Markdown

Summary

Adds Future AGI to the bulleted list of OpenTelemetry-compatible visualization options in src/content/docs/user-guide/observability-evaluation/traces.mdx, alongside Jaeger, Langfuse, AWS X-Ray, Zipkin, and Opik.

Future AGI is an open-source e2e agent engineering and optimization platform that helps you ship self-improving AI agents. It accepts standard OTLP/HTTP at https://api.futureagi.com/tracer/v1/traces, so an existing Strands StrandsTelemetry().setup_otlp_exporter() configuration works unchanged when pointed at the Future AGI endpoint via OTEL_EXPORTER_OTLP_ENDPOINT and OTEL_EXPORTER_OTLP_HEADERS.

What changed

  • One new bullet in the "Common visualization options include:" list.
  • No code, config, or other docs touched.

Smoke test

Verified the Future AGI tracer endpoint accepts OTLP/HTTP from a vanilla Python OTel SDK:

  • POST https://api.futureagi.com/tracer/v1/traces with x-api-key + x-secret-key headers → HTTP 200 OK.
  • A test span with project_name resource attribute landed in the Future AGI dashboard under the named project.

Test plan

  • Astro / mkdocs build passes
  • Maintainer happy with the one-line addition (also open to writing a fuller community integration page under src/content/docs/community/integrations/ if preferred)

🤖 Generated with Claude Code

Adds Future AGI to the bulleted list of OpenTelemetry-compatible
visualization options in the traces page, alongside Jaeger,
Langfuse, AWS X-Ray, Zipkin, and Opik. Future AGI accepts standard
OTLP/HTTP at https://api.futureagi.com/tracer/v1/traces, so existing
Strands StrandsTelemetry().setup_otlp_exporter() configurations work
unchanged when pointed at the Future AGI endpoint.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant