Spectrum-TS

Spectrum-TS has built-in OpenTelemetry instrumentation. Enable it with telemetry: true, then route its OTLP exporter to Agnost with standard OTEL_EXPORTER_OTLP_* environment variables. Note: Spectrum telemetry is exported by the spectrum-ts package itself, so the app must have spectrum-ts installed. The umbrella package includes the official provider packages; install a scoped @spectrum-ts/* package only if the app imports that provider directly.

1. Install

Already have spectrum-ts installed? Skip.

npm install spectrum-ts

Official provider imports:

Provider	Umbrella import	Direct package
Telegram	`spectrum-ts/providers/telegram`	`@spectrum-ts/telegram`
Slack	`spectrum-ts/providers/slack`	`@spectrum-ts/slack`
WhatsApp Business	`spectrum-ts/providers/whatsapp-business`	`@spectrum-ts/whatsapp-business`
iMessage	`spectrum-ts/providers/imessage`	`@spectrum-ts/imessage`
Terminal	`spectrum-ts/providers/terminal`	`@spectrum-ts/terminal`

2. Point Spectrum telemetry at Agnost

Set these before starting the Spectrum app:

export AGNOST_ORG_ID=<your-org-id>
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://otel.agnost.ai/v1/traces
export OTEL_EXPORTER_OTLP_HEADERS="X-Agnost-Org-ID=$AGNOST_ORG_ID"

3. Enable Spectrum telemetry

import { Spectrum } from "spectrum-ts";
import { telegram } from "spectrum-ts/providers/telegram";

const app = await Spectrum({
  projectId: process.env.PROJECT_ID!,
  projectSecret: process.env.PROJECT_SECRET!,
  providers: [
    // Telegram is only an example. Any official Spectrum provider works with
    // the same telemetry config.
    telegram.config({ botToken: process.env.TELEGRAM_BOT_TOKEN! }),
  ],
  telemetry: true,
});

// Optional smoke-test loop only. Spectrum telemetry is enabled above; keep this
// only if you want the sample app to reply to messages.
for await (const [space, message] of app.messages) {
  if (message.content.type !== "text") continue;

  const output = `Echo: ${message.content.text}`;
  await space.send(output);
}

telemetry: true sends Spectrum’s native spans for provider, space, message, content type, and lifecycle metadata. Current Spectrum native spans do not include raw transcript text. If Agnost Chat View must render the actual user/bot messages, emit one additional app-level turn span with agnost.session_id, agnost.user_id, input, and output from your message loop.

Local Sample

npm create spectrum-project@latest clank -- --providers telegram
cd clank

export PROJECT_ID=<spectrum-project-id>
export PROJECT_SECRET=<spectrum-project-secret>
export TELEGRAM_BOT_TOKEN=<telegram-bot-token>
export AGNOST_ORG_ID=<your-org-id>
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://otel.agnost.ai/v1/traces
export OTEL_EXPORTER_OTLP_HEADERS="X-Agnost-Org-ID=$AGNOST_ORG_ID"

Use the provider you need, for example telegram, slack, whatsapp-business, imessage, or terminal. Then set telemetry: true in the generated Spectrum(...) config. Native Spectrum telemetry is enough for Trace View and Metadata. Add a separate turn span only if you need transcript text in Chat View.

Conversation SDKs

OpenTelemetry

MCP Servers

Integrations

1. Install

2. Point Spectrum telemetry at Agnost

3. Enable Spectrum telemetry

Local Sample

References

​1. Install

​2. Point Spectrum telemetry at Agnost

​3. Enable Spectrum telemetry

​Local Sample

​References

1. Install

2. Point Spectrum telemetry at Agnost

3. Enable Spectrum telemetry

Local Sample

References