+ OpenTelemetry Demo with OpenSearch

The following guide describes how to setup the OpenTelemetry demo with OpenSearch Observability using Docker compose or Kubernetes.

Docker compose

Prerequisites

• Docker
• Docker Compose v2.0.0+
• 4 GB of RAM for the application

Running this demo

git clone https://github.com/opensearch-project/opentelemetry-demo.git
cd opentelemetry-demo
docker compose up -d

Services

Once the images are built and containers are started you can access:

• Webstore-Proxy (Via Nginx Proxy): http://nginx:90/ (nginx DNS name needs to be added )
  • Defined here
• Webstore: http://frontend:8080/ (frontend DNS name needs to be added )
  • Defined here
• Dashboards: http://dashboards:5601/ (dashboards DNS name needs to be added )
• Feature Flags UI: http://featureflag:8081/ (featureflag DNS name needs to be added )
  • Defined here
• Load Generator UI: http://loadgenerator:8089/ (loadgenerator DNS name needs to be added)
  • Defined here

OpenSearch has documented the usage of the Observability plugin with jaeger as a trace signal source.

The next instructions are similar and use the same docker compose file.

1. Start the demo with the following command from the repository's root directory:

   docker compose up -d
   

Note: The docker compose --no-build flag is used to fetch released docker images from ghcr instead of building from source. Removing the --no-build command line option will rebuild all images from source. It may take more than 20 minutes to build if the flag is omitted.

Explore and analyze the data With OpenSearch Observability

Review revised OpenSearch Observability Architecture

Start learning OpenSearch Observability using our tutorial

Getting started Tutorial

Service map

Traces

Correlation

Logs