Skip to main content
A service is one service.name that sends server or consumer spans. The Services API returns the request rate, error rate, latency, and health of each service, its operations and dependencies, and the map of calls between services and databases. See Services and releases for how Squasher finds services and sets their health.

Operations

All three operations need the errors:read scope. URL-encode service_name.

Query parameters

Every operation takes a window and an environment: The window is at most 7 days. services.list also takes these parameters:

List services

The JSON is shortened to one service. Rates are percents from 0 to 100. Latencies are in milliseconds. throughput_per_min is requests per minute over the window.

Read one service

  • upstream lists the services that call this service. downstream lists the services it calls. databases lists the database systems it calls, by db.system.name.
  • releases lists the releases of the service that served in the window, newest first. Each item has the same fields as last_release above.
  • series has one point for each granularity bucket.
A service that sent no spans in the window answers with status: "no_data" and empty sections, not an error.

Read the service map

A node id is service:<service.name> or database:<db.system.name>. An edge kind is call (service to service) or database (service to database). source and target are node IDs.

Errors

TypeScript client, CLI, and MCP

Add --json to print the full response. In MCP Code Mode, call search("services") first, then execute with services.list, services.get, or services.map.