Quick Start
Connect an application with a coding agent or manual setup.
Telemetry Machine gives you two ways to connect an application. Both start on the same onboarding screen.
Create your account
- Sign up with your email address and a password.
- Verify your email address. In the browser you signed up in, that signs you in.
- Open an explorer such as Traces. If your organization has no datasets, Telemetry Machine takes you to onboarding.
Option 1Set up with a coding agent
Use this path when a coding agent can edit your application and run commands in its development environment. On the onboarding page, pick your agent in the first step.
Claude Code
-
In a terminal, install the Telemetry Machine plugin. It needs Claude Code 2.1.292 or later. The plugin adds the Telemetry Machine MCP server.
Terminal$ claude plugin install telemetry-machine --marketplace telemetry-machine/agent-skills -
Start Claude Code in your application's folder, run
/mcp, chooseplugin:telemetry-machine:telemetry-machine, and sign in. -
Start onboarding:
Text/mcp__plugin_telemetry-machine_telemetry-machine__onboarding -
Answer its questions. Claude Code instruments your application, creates the datasets and API keys it needs, confirms that data arrives, and answers a first question from your data.
If you stop part-way, run the same command again. It continues from where you stopped.
Other coding agents
-
Add
https://telemetrymachine.com/api/mcpto your agent as a remote MCP server (Streamable HTTP). The onboarding page shows the exact command or configuration for Codex and Cursor. -
Sign in when your agent asks. It opens your browser; approve there.
-
In your application's folder, ask your agent:
TextUse the telemetry-machine MCP server: call get_onboarding_guide and follow it to set up this app.
Keep the onboarding page open to follow progress. It shows when your agent has signed in and lists the datasets it creates. Select one to open its explorer.
Option 2Set up manually
-
Open Create a dataset.
-
Choose the data you want to send: traces, logs, metrics, or events.
-
Name the dataset and choose any optional starter widgets.
-
Create the dataset. Telemetry Machine also creates a starter API key for it.
-
Copy the API key and store it securely.
Its full value is only shown once.
-
Choose the generated setup for the OpenTelemetry Collector, Node.js, or Python. An events dataset gets a
curlcommand instead. -
Add the configuration to your application and run or deploy it.
-
Open the matching explorer and confirm that your data arrives.
A dataset holds one type of data, so the generated setup sends only that type. For a traces dataset it looks like this, with your API key and dataset name filled in:
exporters:
otlp_http:
endpoint: "https://api.telemetrymachine.com"
headers:
X-API-Key: "<your-api-key>"
X-Dataset-Name: "<your-dataset>"
service:
pipelines:
traces:
exporters: [otlp_http]// npm install @opentelemetry/sdk-node @opentelemetry/exporter-trace-otlp-http
import { NodeSDK } from '@opentelemetry/sdk-node';
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
const sdk = new NodeSDK({
traceExporter: new OTLPTraceExporter({
url: 'https://api.telemetrymachine.com/v1/traces',
headers: {
'X-API-Key': '<your-api-key>',
'X-Dataset-Name': '<your-dataset>',
},
}),
// NodeSDK would otherwise export these too.
metricReaders: [],
logRecordProcessors: [],
});
sdk.start();# pip install opentelemetry-sdk opentelemetry-exporter-otlp-proto-http
from opentelemetry import trace
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
provider = TracerProvider()
exporter = OTLPSpanExporter(
endpoint="https://api.telemetrymachine.com/v1/traces",
headers={
"X-API-Key": "<your-api-key>",
"X-Dataset-Name": "<your-dataset>",
},
)
provider.add_span_processor(BatchSpanProcessor(exporter))
trace.set_tracer_provider(provider)Collector versions before v0.144.0 call the exporter otlphttp.
You can repeat the manual wizard to create more datasets for other signal types, services, or environments.
tm-cli
tm-cli is Telemetry Machine's command line, for terminals and CI. Download the build for your OS and architecture from the release manifest, check its sha256, and put tm-cli on your PATH. Then sign in in your browser:
tm-cli auth loginIn CI, set TM_API_KEY to a personal access token instead.