[FEA] Add a Future AGI OTLP telemetry exporter (futureagi)

Open
  • Is something wrong?
#2,489 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@nik13 is already working on this.

Since Oct 29, 2026.

Assessment

This issue has not been assessed yet.

Description

Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

Medium

Please provide a clear description of problem this feature solves

Teams sending NeMo Agent Toolkit traces to Future AGI currently need to configure the generic exporter themselves: an OTLP/HTTP endpoint, two authentication headers (X-Api-Key and X-Secret-Key), and a project_name resource attribute. A named exporter would make that setup discoverable alongside the other observability backends.

Describe your ideal solution

Add a futureagi exporter to nvidia_nat_opentelemetry, following the existing Arize AX and MLflow exporter patterns:

  • project name, API key, secret key, and optional endpoint configuration, with environment-variable fallbacks;
  • uncompressed OTLP/HTTP to the Future AGI /tracer/v1/traces endpoint, with project_name on the resource;
  • an observe guide, a calculator-observability example, a telemetry-exporters table entry, and tests.

Would this be welcome? We will wait for agreement on scope before opening the upstream PR. No additional Future AGI instrumentor dependency is proposed.

Additional context

This follows the earlier request #972, which is closed. We would address the feedback on #1090 rather than reopen the old PR: consistent configuration fields, no unrelated version/evaluation attributes, and the missing example and documentation entries. The eventual commits must satisfy the repository's DCO requirement; this issue does not assert that the prepared branch already does.

I work at Future AGI. AI assistance was used to research and draft this proposal.

Code of Conduct
  • I agree to follow this project's Code of Conduct.
  • I have searched the open feature requests and found no open duplicate; the closed predecessor is linked above.
Dominant language
Python
Stars
2.7k
Forks
814
Avg merge
1d 7h
Merged PRs (30d)
131

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/NeMo-Agent-Toolkit

All issues in NVIDIA/NeMo-Agent-Toolkit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.