SigNoz Cloud - This page is relevant for SigNoz Cloud editions.

Send Demo App Telemetry to SigNoz Cloud in minutes

Want to explore SigNoz without setting up your own app? This quickstart guide walks you through how to spin up a lightweight OpenTelemetry Demo and start sending logs, metrics, and traces to SigNoz Cloud in minutes.

The OpenTelemetry Demo App is a distributed microservices application with built-in telemetry, making it an ideal environment for exploring observability workflows with SigNoz.

Prerequisites

Setup

Step 1: Clone the OpenTelemetry Demo App

git clone https://github.com/SigNoz/opentelemetry-demo-lite.git
cd opentelemetry-demo-lite

Step 2: Start the Demo App

From the root of the opentelemetry-demo-lite directory, run:

OTLP_ENDPOINT=ingest.<region>.signoz.cloud:443 SIGNOZ_INGESTION_KEY=<your-ingestion-key> docker compose up -d

Alternatively, you can create a .env file in the project root with these values:

OTLP_ENDPOINT=ingest.<region>.signoz.cloud:443
SIGNOZ_INGESTION_KEY=<your-ingestion-key>

Then run:

docker compose up -d

Verify the services are running:

docker compose ps -a
Docker containers of OTel Demo App

The application is pre-configured to send telemetry data to SigNoz Cloud automatically.

Step 4: Verify Telemetry in SigNoz Cloud

  1. Navigate to the Services tab — you should see a list of services from the demo app
  2. Use the Service Map to visualize the architecture and request flows
  3. Check the Traces, Logs, and Metrics tabs to explore telemetry data
SigNoz services tab
Services Listed down in SigNoz services tab

You are now successfully sending data to SigNoz Cloud!

Troubleshooting

Enable collector's debug logging

Edit otel-collector-config.yaml and change the log level from info to debug:

service:
  telemetry:
    logs:
      level: debug

Restart with rebuild to apply changes:

docker compose up -d --build

Check the OTel Collector logs for detailed export information:

docker compose logs otel-col

Look for successful export messages or errors like connection failures and authentication issues.

Containers not starting

If containers are failing to start, check the logs for the specific service:

docker compose logs <service-name>

Ensure Docker has adequate memory and no port conflicts exist.

Services not appearing in SigNoz

  • Verify your OTLP_ENDPOINT and SIGNOZ_INGESTION_KEY are set correctly
  • Check network connectivity to the SigNoz endpoint
  • Wait 2-3 minutes after starting the demo app (OpenTelemetry buffers data before sending)

Next Steps

Last updated: February 3, 2026

Edit on GitHub