Skip to content
telemioDeveloper Docs
Open console
DOCUMENTATIONHands-on · QuickstartBrowse integrations ↗
Docs/Developer Connect/Telemetry playground
Hands-on · Quickstart

Your first telemetry lab.

Run the sample application and follow a real trace from your first request to your first dashboard.

AI-READY REFERENCE

Pass this guide to your agent

Short, page-specific instructions for an AI coding assistant.

Markdown ↗
Preview agent instructions 
# Telemio agent instructions — Telemetry playground

Walk the user through the Telemio sample telemetry playground. Identify the sample trace, error, and log signals, then suggest replacing the sample with real OpenTelemetry instrumentation. Avoid embedding secrets in browser scripts or sample snippets. Confirm sample results in the console; do not equate a successful sample with production instrumentation.

Reference: https://telemio.sh/docs/playground.html

Get running in four steps

Requires Node.js 22 or newer. Keep the ingestion secret on your own machine.

01

Create a workspace

Sign in to Telemio Console, choose Sample app during onboarding, and create your workspace.

02

Generate a trusted server ingest key

Use service name telemio-hello-world and environment development. Copy the server ingest-only key when it is first displayed. Do not share it or place it in frontend code.

03

Download and start the local sample

Extract the ZIP, open its folder in Terminal, and create a private .env file. Replace the placeholder with the key from your Telemio workspace.

Shell
cd telemio-hello-telemetry-lab
cp .env.example .env
chmod 600 .env
# Edit .env locally and set TELEMIO_INGEST_KEY
npm start
04

Trigger your first trace

Open http://127.0.0.1:4319 and click Generate a successful trace or Generate an error trace. The backend exports real OTLP/HTTP JSON spans. Look for service telemio-hello-world in your Telemio workspace and inspect its nested spans.

What you will learn

Trace

Follow a request

See a root HTTP span and its nested operation in a single trace.

Debug

Inspect failures

Generate an intentional error with exception metadata and an error status.

Security

Separate frontend and backend

The browser never sees your ingest key. A trusted local server handles OTLP export.

Next: Replace the sample with your own Node.js, Python, browser, mobile or AI-agent instrumentation. Follow the getting-started guide or the agentic runtime reference.