.do
Monitoring

traces

Analyze distributed traces across your entire stack with AI-powered insights. Query billions of traces in milliseconds, identify patterns, and optimize performance with automatic anomaly detection.

traces

Traces.do

Overview

The traces primitive is part of the .do platform's semantic API system. It follows the $.Subject.verb.Object pattern for consistent, intuitive interactions across SDK, CLI, API, and MCP interfaces.

Semantic Pattern

All traces operations follow the semantic $.Traces.verb.Object pattern:

import { $, traces } from 'sdk.do'

// Create resources
await $.Traces.create.Resource({ /* config */ })

// Query data
await $.Traces.get.Data({ /* params */ })

// Update state
await $.Traces.update.Status({ /* changes */ })

Quick Start

import { traces } from 'sdk.do'

// Initialize and use the primitive
const result = await traces.operation({
  // configuration parameters
})

Access Methods

The traces primitive is accessible through multiple interfaces:

SDK

TypeScript/JavaScript library for programmatic access:

import { traces } from 'sdk.do'
await traces.method({ /* ... */ })

SDK Documentation

CLI

Command-line interface for terminal operations:

do traces <command> [options]

CLI Documentation

API

REST/RPC endpoints for HTTP integration:

curl -X POST https://api.do/v1/traces \
  -H "Content-Type: application/json" \
  -d '{"key":"value"}'

API Documentation

MCP

Model Context Protocol for AI assistant integration:

Use traces primitives with AI assistants via MCP

MCP Documentation

See other primitives in the monitoring category.