Skip to content

docs: add Future AGI to Observability integrations#790

Open
SuhaniNagpal7 wants to merge 1 commit into
pipecat-ai:mainfrom
SuhaniNagpal7:add-future-agi-observability
Open

docs: add Future AGI to Observability integrations#790
SuhaniNagpal7 wants to merge 1 commit into
pipecat-ai:mainfrom
SuhaniNagpal7:add-future-agi-observability

Conversation

@SuhaniNagpal7
Copy link
Copy Markdown

Summary

Adds Future AGI to the Observability category in two places, mirroring how OpenInference and Langfuse are documented:

  1. api-reference/server/services/community-integrations.mdx — a new row in the Observability table, alongside OpenInference and Finchvox.
  2. api-reference/server/utilities/opentelemetry.mdx — a ### Future AGI subsection right after the existing ### OpenInference block, with the same shape (one paragraph + a single repository bullet + a pointer back to the community-integrations page).

What the integration does

Future AGI is an open-source e2e agent engineering and optimization platform that helps you ship self-improving AI agents. The traceAI-pipecat package converts Pipecat span attributes (gen_ai.system, gen_ai.request.model, gen_ai.usage.*, transcript, input/output) into Future AGI conventions, so an existing Pipecat OTEL setup routes traces to the Future AGI dashboard with one extra call to enable_http_attribute_mapping().

Smoke test

Verified end-to-end against the Future AGI tracer endpoint with traceai-pipecat 0.1.1:

  • register(project_type=OBSERVE, project_name='pipecat-doc-smoke', transport=HTTP) → OK
  • enable_http_attribute_mapping() → returned True
  • A manual span carrying Pipecat-shaped attributes (gen_ai.system, gen_ai.request.model, input, output) flushed via trace_provider.force_flush()HTTP 200 OK to https://api.futureagi.com/tracer/v1/traces
  • The pipecat-doc-smoke project surfaced in the Future AGI dashboard

Note on the demo-video requirement

The COMMUNITY_INTEGRATIONS.md submission process mentions a 30-60s demo video showing core functionality and interruption handling. This is a community observability integration (an OTel attribute mapper), not a service integration on the audio path — there's no audio interaction or interruption to demo. Happy to record a short clip showing traces flowing into the dashboard if maintainers prefer.

Test plan

  • npx prettier --check passes on both edited files
  • npx mint broken-links passes
  • Maintainer review of placement (Observability row + parallel ### Future AGI subsection in opentelemetry.mdx)

🤖 Generated with Claude Code

Adds a row to the Observability table in
api-reference/server/services/community-integrations.mdx and a
parallel ### Future AGI subsection in
api-reference/server/utilities/opentelemetry.mdx (mirroring the
OpenInference subsection), pointing readers at the traceAI-pipecat
package.

The traceAI-pipecat package converts Pipecat span attributes
(gen_ai.system, gen_ai.request.model, gen_ai.usage.*, transcript,
input/output) into Future AGI conventions so existing Pipecat OTEL
setups can route traces to Future AGI with one extra call to
enable_http_attribute_mapping().
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