opentelemetry-collector | OpenTelemetry Collector | Analytics library

What you're doing in the docker run command is the following mounting:

${PWD}/local/otel-config.yaml on the local host to /otel-local-config.yaml from inside the docker

You can achieve same behavior with volumes option from docker compose:

volumes:

• "${PWD}/local/otel-config.yaml":/otel-local-config.yaml

Grafana 7.5 and later can talk to Tempo natively, and no longer need the tempo-query proxy. I think this explains what is happening, Grafana is attempting to use the Tempo-native API against tempo-query, which exposes the Jaeger API instead. Try changing the Grafana datasource in datasource.yml to http://tempo:3200.

I finally found an answer, thanks to this post

You need to specify the full path of the file you want to mount. If not, because docker will not find the fill, it will create an empty directory based on the name of the file !

An issue was entered for OpenTelemetry Collector that would solve my main concerns of using secrets in environment variables.

Until then, the author of the issue suggest environment variable expansion mechanism as a workaround.

So if you put your token in an environment variable ELASTIC_APM_TOKEN, then you could reference it in your ConfigMap like so:

No, although the binary is same there is a difference in terms of deployment. The agent is collector instance running on the same host as application that emits the telemetry data. Agent then forwards this data to a Gateway (One or more instances of collectors which receive data from multiple agents). And then data is send to configured backends (Jaeger, Zipkin, Private vendors etc...)

Good job so far. Your pipeline is almost good, however, the grok pattern needs some fixing and you have some orphan curly braces. Here is a working example:

AppDynamics have a fork of contrib project here where there is an exporter but it isn't clear if it has been finished

The demo you tried is using older configuration and opencensus which should be replaced with otlp receiver. Having said that this is a working example https://github.com/open-telemetry/opentelemetry-js/tree/master/examples/collector-exporter-node/docker So I'm copying the files from there:

docker-compose.yaml

Thing is, you should use opentelemetry collector if you use opentelemetry exporter.

Pls see schema in attachment

Also I created a gist, which will help you to setup pls see

https://gist.github.com/AndrewGrachov/11a18bc7268e43f1a36960d630a0838f

(just tune the values, export to jaeger-all-in-one instead of separate + cassandra, etc)