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.
Couple of items to ease maintenance - [ ] Add SIG Approvers to their language(s) - [ ] Add authors of services to codeowners so they get pinged for PRs,...
With #872 merged, we have several docs updates that need to be done. See https://github.com/open-telemetry/opentelemetry-demo/pull/872/#issuecomment-1627605516 for details.
# Feature Request Demo should conform to OTEL standard regarding feature flag. Namely: A flag evaluation SHOULD be recorded as an Event on the span during which it occurred. https://opentelemetry.io/docs/specs/otel/trace/semantic_conventions/feature-flags/#convention...
# Feature Request Hello Team. I've been playing a bit with OpenTelemetry demo and started to think if there is any specific reason why we don't have any database instance...
Dotnet should have non instrumentation library based auto instrumentation examples. https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation
# Feature Request Currently, the frontend/webstore component doesn't really give people much information about what's actually happening in terms of backend instrumentation. Errors and latency that are induced by failure...
We need a new service to demonstrate a couple of concepts: - Injecting instrumentation using k8s operator - Custom Java metrics/logs My suggestion would be for a small Java app...
The load generator emits tracebacks that aren't structured well (1 line per message), causing problems when trying to ingest them to a logging system.
After running a 4-week test on a stable EKS cluster using m6i.large nodes I have found the following services to be experiencing memory leaks: - [ ] `emailservice` (severe) -...
# Feature Request Currently, auto-instrumentation is injected via [Docker file](https://github.com/open-telemetry/opentelemetry-demo/blob/main/src/adservice/Dockerfile). While having it for Docker deployment is fine, for Kubernetes deployment, it is a preferred option to get it injected...