opentelemetry-proto VS opentelemetry-collector

We then modified the benchmark to encode our example data which is an opentelemetry trace data.

There are 2 collector types: the core and the contrib. I have used the contrib as it features the splunk_hec exporter.

Lightstep ingests data in native OpenTelemetry Protocol (OTLP) format, so we will use the OTLP Exporter. The exporter can be called either otlp or follow the naming format otlp/. We could call it otlp/bob if we wanted to. We're calling our exporter otlp/ls to signal to us that we are using the OTLP exporter to send the data to Lightstep.

Then, we set up a batch processor that batches up the spans together and every 1 second sends the batch forward. In production, you would want more than 1 second, but I set this here to 1 second for instant feedback in Jaeger.

Batch allows for metrics, traces etc to be batched into bundles. The default is 8192 and then it will send, the timeout is the max time before sending regardless. I'd highly recommend utilising batches if you're dealing with high volumes of traffic.

There were a bunch of alternatives to solve this before, like grafana agent [0], vm agent [1] or opentelemetry collector [2].

[0] - https://github.com/grafana/agent

[1] - https://github.com/VictoriaMetrics/VictoriaMetrics/tree/mast...

[2] - https://github.com/open-telemetry/opentelemetry-collector

You can find detailed information about these processors and more in OpenTelemetry Collector GitHub repo.

You can then configure an Opentelemetry Client SDK installation or OpenTelemetry Collector to use Jaeger exporter and send trace data to this local Jaeger.

open-telemetry/opentelemetry-collector (Go): OpenTelemetry Collector