This demo is already configured to send telemetry data (logs, metrics, and traces) to Parseable through two methods:
- OpenTelemetry Collector: Exports logs, metrics, and traces directly to Parseable
- Fluent Bit: Collects container logs and forwards them to Parseable
Simply run the application using Docker Compose as described in the Docker deployment section, and both the OpenTelemetry Collector and Fluent Bit will automatically export telemetry to the Parseable instance included in the deployment.
Parseable is accessible at http://localhost:8000 with default credentials (username: admin
, password: admin
).
To use Fluent Bit as the telemetry collector instead of the OpenTelemetry Collector:
-
Use the Fluent Bit docker-compose file:
docker-compose -f docker-compose-fluent-bit.yml up -d
-
Update the
.env
file to point services to Fluent Bit:OTEL_COLLECTOR_HOST=fluent-bit
Fluent Bit will collect OpenTelemetry data on ports 4317 (gRPC) and 4318 (HTTP) and forward it to Parseable with proper stream separation (logs, metrics, traces).
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.
Our goals are threefold:
- Provide a realistic example of a distributed system that can be used to demonstrate OpenTelemetry instrumentation and observability.
- Build a base for vendors, tooling authors, and others to extend and demonstrate their OpenTelemetry integrations.
- Create a living example for OpenTelemetry contributors to use for testing new versions of the API, SDK, and other components or enhancements.
We've already made huge progress, and development is ongoing. We hope to represent the full feature set of OpenTelemetry across its languages in the future.
If you'd like to help (which we would love), check out our contributing guidance.
If you'd like to extend this demo or maintain a fork of it, read our fork guidance.
You can be up and running with the demo in a few minutes. Check out the docs for your preferred deployment method:
For detailed documentation, see Demo Documentation. If you're curious about a specific feature, the docs landing page can point you in the right direction.
We welcome any vendor to fork the project to demonstrate their services and adding a link below. The community is committed to maintaining the project and keeping it up to date for you.
To get involved with the project see our CONTRIBUTING documentation. Our SIG Calls are every other Wednesday at 8:30 AM PST and anyone is welcome.
- Juliano Costa, Datadog
- Mikko Viitanen, Dynatrace
- Pierre Tessier, Honeycomb
- Roger Coll, Elastic
For more information about the maintainer role, see the community repository.
- Cedric Ziel, Grafana Labs
- Shenoy Pratik, AWS OpenSearch
For more information about the approver role, see the community repository.
For more information about the emeritus role, see the community repository.