Skip to main content
reopt Handbook
reopt Handbook
Enterprise Eve Agent Development

Core Architecture

Ch1. Eve Mental ModelCh2. Source Code AtlasCh3. Project Layout and DiscoveryCh4. Compiler and Runtime Graph

Agent Quality Design

Ch5. agent.ts, Models, CompactionCh6. Context, Skills, Dynamic CapabilitiesCh7. Tools, Approval, ConnectionsCh8. Sandbox Secure Runtime

Operational Runtime

Ch9. Channels, Auth, StreamingCh10. Subagents, Workflows, Remote AgentsCh11. Schedules, State, HooksCh12. Evals and Quality Gates

Production Operations

Ch13. Observability and DeploymentCh14. Enterprise PatternsCh15. Migration and Governance

Appendix

Official Docs CrosswalkVerification ReportUpdates
Handbook›엔터프라이즈 Eve 에이전트›Ch13. Observability and Deployment
한국어English

Ch13. Observability and Deployment

Operate Eve with OpenTelemetry, Workflow tags, deployment checklists, health checks, and production runbooks.

Key takeaways

  • Eve observability needs session, turn, step, tool, sandbox, subagent, and model-usage views.
  • OpenTelemetry, Workflow tags, and runtime hooks are complementary surfaces.
  • Vercel and self-host deployments both need artifact, health, session, and stream verification.

Durable agents cannot be operated with HTTP request logs alone. You need to see where a run is parked, what step failed, which tool ran, which sandbox backend was used, and how much model usage accumulated.

Three Observability Surfaces

SurfaceLocationUse
Workflow run tagsframework emittedAgent Runs and session tree
OpenTelemetryagent/instrumentation.tsexport spans to observability backend
Runtime hooksagent/hooks/**audit, metrics, warehouse ingestion

instrumentation.ts

agent/instrumentation.ts
import { defineInstrumentation } from "eve/instrumentation";
import { registerOTel } from "@vercel/otel";

export default defineInstrumentation({
  setup: ({ agentName }) =>
    registerOTel({
      serviceName: agentName,
    }),
  recordInputs: false,
  recordOutputs: false,
});

Official docs note that inputs and outputs can be recorded by default. In sensitive environments, explicitly review recordInputs, recordOutputs, exporter destination, retention, and access.

Runtime Context Enrichment

export default defineInstrumentation({
  events: {
    "step.started"(input) {
      return {
        runtimeContext: {
          "tenant.id": input.session.auth.current?.attributes.tenantId ?? "unknown",
          "channel.kind": input.channel.kind,
        },
      };
    },
  },
});

Avoid secrets, PII, and unbounded cardinality.

Workflow Tags

Eve emits reserved $eve.* attributes for workflow runs.

TagMeaning
$eve.typesession, turn, subagent
$eve.parentimmediate parent session
$eve.rootroot session
$eve.subagentsubagent node id
$eve.triggerchannel kind
$eve.titlefirst-message derived title
$eve.modelturn model id
$eve.input_tokenscumulative input tokens
$eve.output_tokenscumulative output tokens
$eve.tool_counttool count

These are helpful but should not be the only audit source. Use hooks for mandatory audit ledgers.

Vercel Deployment

eve build
vercel deploy

On Vercel, Eve emits Vercel Build Output, Workflow runs on Vercel Workflow, and defaultBackend() selects Vercel Sandbox.

Smoke checks:

curl https://<deployment>/eve/v1/health
curl -X POST https://<deployment>/eve/v1/session \
  -H 'content-type: application/json' \
  -d '{"message":"Hello from production"}'
curl https://<deployment>/eve/v1/session/<sessionId>/stream

Self-host Deployment

eve build
PORT=3000 eve start --host 0.0.0.0
ConcernStandard
workflow statepersistent .workflow-data
model authAI Gateway key or direct provider key
route authreplace Vercel OIDC with host-valid auth
sandboxDocker, microsandbox, or custom backend
schedulesensure Nitro scheduled tasks run
logsprocess manager and log collector
TLS/routingreverse proxy or platform

Build Artifact Review

ArtifactCheck
.eve/diagnostics.jsonno unexpected warnings/errors
agent-discovery-manifest.jsonexpected files only
compiled-agent-manifest.jsontools, connections, channels, schedules, subagents
module-map.mjscompiled module resolution

Runtime Runbook

SymptomCheck
production 401route auth and placeholder removal
stuck in session.waitingapproval, question, or OAuth pending
tool not visibleeve info, dynamic resolver event, disabled default
missing subagent resultchild stream and parent proxy input request
sandbox command failedbackend, network policy, bootstrap
cost spiketoken tags, tool count, compaction
trace missinginstrumentation setup and exporter

Production SLO Candidates

SLOMeasurement
session start successPOST /session 2xx ratio
turn completionturn.completed / started
no failed stepstep.failed rate
approval latencyinput.requested to answer
model latencystep.started to step.completed
cost per tasktokens + tool infrastructure
sandbox setup latencyfirst sandbox use
eval pass rateCI and scheduled evals

Deployment Checklist

GateStandard
buildeve build succeeds
diagnostics.eve/diagnostics.json clean
authproduction route auth fail-closed
secretsnot present in artifacts or workspace
sandboxbackend and network policy explicit
evaleve eval --strict passes
smokehealth, session, and stream checks pass
observabilityOTel or hook audit works
rollbackmodel/prompt/tool rollback documented

Related docs

Ch8. Sandbox Secure Runtime

Turn Eve sandbox trust boundaries, backends, network policy, credential brokering, and workspace lifecycle into operating standards.

Ch15. Migration and Governance

Migrate existing agents into Eve and establish enterprise governance for agent portfolios.

Vercel Deployment

Enterprise Project Architecture · Organize project, environment, preview, and production deployment rules for enterprise teams.

Sandbox Tool Runtime

Vercel Enterprise AI Platform · Isolate code, file, browser, and shell execution for AI agents.

Ch5. Observability and SLOs

LLMOps and AgentOps in Production · Collect model, tool, and policy execution as traceable signals and operate them through SLOs

Ch12. Evals and Quality Gates

Use Eve eval runner and assertion surfaces to prevent agent regressions in CI and production.

Ch14. Enterprise Patterns

Combine Eve features into support, research, code, back-office, analytics, and incident-response agent patterns.

On this page

Three Observability Surfacesinstrumentation.tsRuntime Context EnrichmentWorkflow TagsVercel DeploymentSelf-host DeploymentBuild Artifact ReviewRuntime RunbookProduction SLO CandidatesDeployment Checklist