New component: Lightstep receiver

[kostz]

The purpose and use-cases of the new component

Hello community, we have just released a Lightstep receiver https://github.com/zalando/otelcol-lightstep-receiver , and I'm wondering if we can include this into contrib pack someday.

This component receives tracing traffic from lightstep_tracer_(go|python|js), converts it to open telemetry and propagates via tracing pipeline.

Also here's Zalando engineering blog post introducing the component.

Example configuration for the component

receivers:
  lightstepreceiver:
    protocols:
      pbgrpc:
        endpoint: "0.0.0.0:4317"
      pbhttp:
        endpoint: "0.0.0.0:4327"
      thrift:
        endpoint: "0.0.0.0:4417"

Telemetry data types supported

traces

Code Owner(s)

No response

Sponsor (optional)

No response

Additional context

No response

[atoulme]

I note you use port 4317 for your gRPC endpoint ; 4317 is a registered IANA port for OTLP traffic: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=4317

[kostz]

https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=4317

alright, makes sense, will change ports in next release

@atoulme going forward is there any process about offering new component, or just this ticket is enough to start the discussion?

[atoulme]

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components has the steps. This issue is the first step.