History

Ian Quick d0d7f138d0 Adds format option to the zipkin exporter (#409 ) Adds an option to the zipkin exporter to support different formats. Currently json and proto are supported with json being the default value.		2019-11-07 14:25:12 -08:00
..
README.md	Example: Add back health check in the agent (#382 )	2019-10-07 13:58:12 -07:00
docker-compose.yaml	Example: Add back health check in the agent (#382 )	2019-10-07 13:58:12 -07:00
otel-agent-config.yaml	Fix agent configuration in the example (#402 )	2019-10-17 13:19:04 -07:00
otel-collector-config.yaml	Adds format option to the zipkin exporter (#409 )	2019-11-07 14:25:12 -08:00
prometheus.yaml	Add collecting metrics to the examples (#253 )	2019-08-13 09:26:29 -07:00

README.md

OpenTelemetry Collector Demo

IMPORTANT: This is a pre-released version of the OpenTelemetry Collector.

Typical flow of tracing and metrics data with OpenTelemetry Collector: tracing and metrics data initially received by OpenTelemetry Agent and then sent to OpenTelemetry Collector using OC data format. The OpenTelemetry Collector then sends the data to the backend, in this demo Jaeger, Zipkin, and Prometheus.

This demo uses docker-compose and runs against locally built docker images of OpenTelemetry Collector. In order to build the docker images use the commands below from the root of the repo:

make docker-otelcol

To run the demo, switch to the examples/demo folder and run:

docker-compose up

Open http://localhost:16686 to see the data on the Jaeger backend, http://localhost:9411 to see the data on the Zipkin backend, or http://localhost:9090 to see data on the Prometheus backend (Note that it may take some time for the application metrics to appear on the Prometheus dashboard).

To clean up any docker container from the demo run docker-compose down from the examples/demo folder.