Wire GenAI telemetry: settings surface, service name, and agent names (N3 WP4)

Browse Source

Why: spans now follow the OTel GenAI convention (Agent-Native#32); the
product needs the settings surface for the exporter, a meaningful
service.name, and per-profile agent names.
Evidence: go test -count=1 ./... green; TestTelemetryFlagsDefaults
(otlpEndpoint registered default empty = no export, serviceName
default agent-system-backend); nested pins carry the convention work.
Impact: nothing is exported unless telemetry.otlpEndpoint (or the env
var) is set; agent spans are named by profile id.
Refs: Agent-Native#32, Agent-Squad#36, N3 plan WP4

...

This commit is contained in:

weichen

2026-10-07 15:41:01 +00:00

parent dcd7c9a444

commit 904742ca4b

8 changed files with 33 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

deps/agent-native

Vendored

+1 -1

Submodule deps/agent-native updated: 79e1a8fa85...fe0c4a9f82

deps/agent-squad

Vendored

+1 -1

Submodule deps/agent-squad updated: 90077b6601...f38cf7c441