opentelemetry-demo
opentelemetry-demo copied to clipboard
This repository contains the OpenTelemetry Astronomy Shop, a microservice-based distributed system intended to illustrate the implementation of OpenTelemetry in a near real-world environment.
The following is a list of requirements that we need to evaluate before declaring v1 for trace telemetry. These requirements are across the entire application; Not all services will meet...
The following is a list of requirements that we need to evaluate before declaring v1 for trace telemetry. These requirements are across the entire application; Not all services will meet...
The following is a list of requirements that we need to evaluate before declaring v1 for trace telemetry. These requirements are across the entire application; Not all services will meet...
**Objective** Create an 'admin service' written in PHP for the web store. The following features should be supported: - Authentication for 'admin users' - UI for CRUD operations on items...
# Feature Request the docker-compse current use `build` command to create the image, it often occur unexpected problem when someone want to take a look the demo, like #178 #170...
used wrong env `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`, cart-service can't connect to OTLP **but no error log** ``` ➜ charts git:(wph95/otel-demo) ✗ kc logs demo-cart-service-57f754d46f-hmj7m Connecting to Redis: demo-redis:6379,ssl=false,allowAdmin=true,abortConnect=false Successfully connected to Redis Performing...
## helm chart - [ ] demo-webstore - [ ] otelcol - [ ] jaeger - [ ] Prometheus - [ ] document - [ ] Multi-node (load balancing, replica...
Some services have OpenTelemetry author licensing while others like the shipping service have no licensing. We need consistent licensing across our new services including: the currency service, feature flag service,...
# Question Is it possible to reduce `featureflagservice`'s memory footprint? Everything in the stack is pretty light except for featureflagservice, which consumes 1.5GB+ memory. ``` CONTAINER ID NAME CPU %...
In order to provide some guidelines for monitoring, we should define SLOs for key user journeys through the application, and use [OpenSLO](https://github.com/OpenSLO/OpenSLO) to define them.