Skip to main content

​
Lifecycle Overview

Use Observe.flush() and Observe.shutdown() to control when finished spans are exported and when the SDK releases tracing resources.

​
Flush

Observe.flush() forces the current provider to export finished spans.
Flush spans
await Observe.flush();
Use flush() when the process may terminate before the batch exporter sends spans in the background:
EnvironmentGuidance
CLI scriptsFlush before process exit
CI jobsFlush before the job step exits
Serverless handlersFlush before returning when spans were created immediately before exit
Long-running web serversPrefer graceful shutdown hooks instead of flushing on every request
Flushing inside every web request can add latency. In long-running services, let the batch processor export normally and flush during shutdown.

​
Shutdown

Observe.shutdown() disables instrumentations, shuts down the provider, and clears SDK state so the process can initialize again with different options.
Shut down tracing
await Observe.shutdown();
Use shutdown when the process owns the provider lifecycle:
Handle graceful shutdown
import { Observe } from "@asymptote/sdk";

process.on("SIGTERM", async () => {
  await Observe.shutdown();
  process.exit(0);
});

​
Reinitialization

Observe.initialize() rejects conflicting reinitialization while the SDK is active. To change exporter settings, shut down first:
Reinitialize with a new exporter
await Observe.shutdown();

Observe.initialize({
  otlpEndpoint: process.env.OTEL_EXPORTER_OTLP_ENDPOINT,
});
If the SDK is already initialized, a later Observe.initialize({ instrumentModules }) call patches additional modules without replacing the provider.

​
Short-Lived Example

Short-lived job example
import { Observe } from "@asymptote/sdk";

Observe.initialize({
  apiKey: process.env.ASYMPTOTE_API_KEY,
});

const run = Observe.observe({ name: "agent.job" }, async () => {
  return runAgentJob();
});

await run();
await Observe.flush();