Metrics

Agent SDK for Go records OpenTelemetry metrics for agent API calls and runtime operations. Metrics are no-op by default until you wire an OTLP exporter.

Wire OTLP

Use WithObservabilityConfig — the same block configures traces, metrics, and logs:

a, err := agent.NewAgent(
    agent.WithLLMClient(llmClient),
    agent.WithObservabilityConfig(&agent.ObservabilityConfig{
        Endpoint: "collector:4317",
        Protocol: agent.OTLPProtocolGRPC,
        Insecure: true,
        // DisableMetrics: true, // opt out of metrics only
    }),
)
defer a.Close()

Apply the same WithObservabilityConfig on both NewAgent and NewAgentWorker. LLM calls, tool executions, and memory operations run as Temporal activities on the worker — without matching config, those spans and metrics are silently dropped and never reach your collector.

Bring your own metrics

import "github.com/agenticenv/agent-sdk-go/pkg/observability"

metrics, err := observability.NewMetrics(
    observability.WithName("my-service"),
    observability.WithEndpoint("collector:4317"),
    observability.WithInsecure(true),
)

a, err := agent.NewAgent(
    agent.WithLLMClient(llmClient),
    agent.WithMetrics(metrics),
)

When WithObservabilityConfig enables metrics, any WithMetrics value is replaced by the OTLP client built from config. For advanced tuning (metrics export interval, headers, sampling), use observability.NewMetrics with observability.Option directly.

Agent API metrics

Emitted by Agent.Run and Agent.Stream:

Metric	Kind	Description
`agent.run.started`	counter	Each `Run` invocation
`agent.run.completed`	counter	Successful run
`agent.run.failed`	counter	Failed run — includes `error` attribute
`agent.run.duration_ms`	histogram	Run wall-clock time in ms
`agent.stream.started`	counter	Each `Stream` invocation
`agent.stream.dispatched`	counter	Workflow successfully dispatched
`agent.stream.failed`	counter	Dispatch failed
`agent.stream.duration_ms`	histogram	Stream dispatch wall-clock time in ms

Stream metrics cover the dispatch phase — not per-token streaming duration.

Runtime metrics

Emitted per LLM call, tool execution, retriever search, and memory operation on the in-process, Temporal, and Restate runtimes.

LLM

Metric	Kind	Description
`agent.llm.call.started`	counter	LLM call started
`agent.llm.call.completed`	counter	LLM call succeeded
`agent.llm.call.failed`	counter	LLM call failed
`agent.llm.latency_ms`	histogram	LLM wall-clock time in ms
`agent.llm.tokens.input`	histogram	Prompt tokens when provider reports usage
`agent.llm.tokens.output`	histogram	Completion tokens when provider reports usage

Tools

Metric	Kind	Description
`agent.tool.call.started`	counter	Tool execute started
`agent.tool.call.completed`	counter	Tool execute succeeded
`agent.tool.call.failed`	counter	Tool execute failed
`agent.tool.latency_ms`	histogram	Tool wall-clock time in ms

Retriever

Metric	Kind	Description
`agent.retriever.call.started`	counter	Retriever search started
`agent.retriever.call.completed`	counter	Retriever search succeeded
`agent.retriever.call.failed`	counter	Retriever search failed
`agent.retriever.latency_ms`	histogram	Search wall-clock time in ms

Memory

Metric	Kind	Description
`agent.memory.recall.*`	counter + histogram	Recall load operations
`agent.memory.store.*`	counter + histogram	Store operations
`agent.memory.dedup.*`	counter + histogram	Semantic dedup lookups
`agent.memory.extract.*`	counter + histogram	Run-end extraction (`StoreModeAlways`)

Each memory operation family has .started, .completed, .failed counters and a .latency_ms histogram.

Common attributes

Runtime metrics include attributes when available:

Attribute	Values
`model`	LLM model name
`provider`	`openai`, `anthropic`, `gemini`
`tool`	Tool name
`retriever`	Retriever name
`memory.kind`	Memory record kind
`memory.dedup`	Dedup decision metadata

Export to Prometheus

The SDK pushes OTLP metrics — it does not expose a Prometheus scrape endpoint directly. Use the OpenTelemetry Collector as a bridge: receive OTLP from the SDK and expose a /metrics endpoint for Prometheus to scrape. Minimal otel-collector-config.yaml:

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: "0.0.0.0:4317"

exporters:
  prometheus:
    endpoint: "0.0.0.0:8889"   # Prometheus scrapes this

service:
  pipelines:
    metrics:
      receivers: [otlp]
      exporters: [prometheus]

Prometheus scrape_configs entry:

scrape_configs:
  - job_name: agent-sdk
    static_configs:
      - targets: ["otel-collector:8889"]

The agent exports to localhost:4317 (OTLP gRPC), the collector bridges to Prometheus on :8889:

agent.WithObservabilityConfig(&agent.ObservabilityConfig{
    Endpoint:      "localhost:4317",
    Protocol:      agent.OTLPProtocolGRPC,
    Insecure:      true,
    DisableTraces: true, // metrics only
    DisableLogs:   true,
})

Telemetry vs metrics

	Telemetry (`Result.Telemetry`)	OTLP metrics
Scope	Per-run summary on the result	Continuous export to collector
Use	App logging, eval assertions	Dashboards, alerts, SLO tracking
Setup	Always populated — no config	Requires `WithObservabilityConfig` or `WithMetrics`

See Telemetry.

Example

Observability

OTLP traces, metrics, and logs

Tracing

Distributed spans for the same operations

Token Usage

Per-run token totals on AgentRunResult

Overview

Getting Started

Runtimes

Features

Advanced

Observability

Testing & Evaluation

Production

Reference Apps

Wire OTLP

Bring your own metrics

Agent API metrics

Runtime metrics

LLM

Tools

Retriever

Memory

Common attributes

Export to Prometheus

Telemetry vs metrics

Example

Observability

Tracing

Token Usage

​Wire OTLP

​Bring your own metrics

​Agent API metrics

​Runtime metrics

​LLM

​Tools

​Retriever

​Memory

​Common attributes

​Export to Prometheus

​Telemetry vs metrics

​Example

Observability

​Related

Tracing

Token Usage

Wire OTLP

Bring your own metrics

Agent API metrics

Runtime metrics

LLM

Tools

Retriever

Memory

Common attributes

Export to Prometheus

Telemetry vs metrics

Example

Related