Onboarding Guide
This guide walks you through setting up Monoscope: create an account, get an API key, integrate an SDK, and start monitoring your API. The whole process takes about 5 minutes.
Prefer video? Here’s a walkthrough:
Steps
① Create an Account
Sign up at app.monoscope.tech using Google, GitHub, or email.

② Create a New Project
After signing up, you’ll be guided through creating your first project. You can update all of these values later.
-
About you: A quick survey to help us tailor your experience.

-
Setup project: Choose a server location and the features you’ll be exploring.

-
Create endpoint: Add an endpoint to monitor and optionally choose the request type.

-
Set notifications: Get alerts via Slack, Discord, email, or SMS when something goes wrong (optional).

-
Add member: Invite teammates to the project (optional).

-
Integration examples: See sample code for your framework (optional).

-
Plan: Choose your billing plan (required).

Click Proceed to create your project. You'll be taken to the dashboard.
③ Get Your API Key
An API key is generated automatically when you create a project. To find it or create additional keys, click API Keys in the bottom-left of the dashboard.

Create separate API keys for each environment (development, staging, production) to keep your data isolated.

④ Integrate an SDK
Add a Monoscope SDK to your application to start sending telemetry data. We have native SDKs for 17+ frameworks, plus OpenTelemetry support for any language.
Find your framework in the SDK Guides: Node.js, Python, Go, PHP, .NET, Java, and more. If your language isn't listed, use OpenTelemetry to integrate directly.
Need help? Email us and we’ll get you set up.
⑤ Test Your Integration
Verify everything works by sending test data with telemetrygen before deploying.
Install telemetrygen
First, install the telemetrygen tool based on your operating system:
# Using Homebrew
brew install telemetrygen
# Or download directly
curl -LO https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/latest/download/telemetrygen_darwin_amd64
chmod +x telemetrygen_darwin_amd64
sudo mv telemetrygen_darwin_amd64 /usr/local/bin/telemetrygen
# Download the binary
curl -LO https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/latest/download/telemetrygen_linux_amd64
chmod +x telemetrygen_linux_amd64
sudo mv telemetrygen_linux_amd64 /usr/local/bin/telemetrygen
# Download from PowerShell
Invoke-WebRequest -Uri https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/latest/download/telemetrygen_windows_amd64.exe -OutFile telemetrygen.exe
# Run using Docker
docker run --rm -it ghcr.io/open-telemetry/opentelemetry-collector-contrib/telemetrygen:latest \
traces --otlp-insecure \
--otlp-endpoint otel.monoscope.tech:4317 \
--otlp-header="x-api-key=YOUR_API_KEY"
Send Test Data
Once installed, you can send test traces to monoscope using your API key:
# Send test traces
telemetrygen traces \
--otlp-insecure \
--otlp-endpoint otel.monoscope.tech:4317 \
--otlp-header="x-api-key=YOUR_API_KEY" \
--traces 10 \
--rate 2
Replace YOUR_API_KEY with the key from Step 3.
Command Options
-
--traces 10: Number of traces to generate (default: 1) -
--rate 2: Number of traces per second (default: 1) -
--duration 30s: How long to generate traces (e.g., 30s, 1m, 5m) -
--service-name "test-service": Custom service name for the traces -
--span-name "test-operation": Custom span name for the operations
Example: Simulate Different Scenarios
# Simulate a service with normal traffic
telemetrygen traces \
--otlp-insecure \
--otlp-endpoint otel.monoscope.tech:4317 \
--otlp-header="x-api-key=YOUR_API_KEY" \
--service-name "payment-service" \
--span-name "process-payment" \
--duration 1m \
--rate 5
# Simulate errors (with status codes)
telemetrygen traces \
--otlp-insecure \
--otlp-endpoint otel.monoscope.tech:4317 \
--otlp-header="x-api-key=YOUR_API_KEY" \
--service-name "auth-service" \
--span-name "authenticate" \
--status-code "ERROR" \
--traces 5
Check the API Log Explorer in your dashboard — test traces should appear within a few seconds.
⑥ Acknowledge Endpoints or Anomalies
As Monoscope receives traffic, it auto-detects your API endpoints (visible in Explorer) and anomalies (visible in Changes & Errors). Acknowledge each endpoint to tell Monoscope what’s expected — this enables accurate anomaly detection and scheduled reports.

Dashboard Overview
| Tab | What it does |
|---|---|
| Get Started | Onboarding checklist for your integration |
| Dashboard | Analytics overview: requests, anomalies, latency, and errors |
| Endpoints | All detected API endpoints |
| API Log Explorer | Search and filter request logs, create alerts |
| Changes & Errors | Detected anomalies and errors |
| Outgoing Integrations | External API calls your service makes |
| API Tests | Create and schedule HTTP response validation tests |
| Reports | Email report history and frequency settings |