Feature - OpenTelemetry Exporter

[atrauzzi]

It probably goes without saying that every OpenTelemetry library should should ship an OpenTelemetry exporter. 😄

The benefit to the PHP library in this would be that at some point, pure OpenTelemetry configurations are going to be possible, and desirable. Having an "ecosystem-native" exporter ensures that the PHP library doesn't contribute any delay towards widespread adoption.
It also helps simplify setup for newcomers by not forcing them into ecosystems and terminology outside of OpenTelemetry.

[bobstrecansky]

@atrauzzi - are you planning on working on this effort?

[atrauzzi]

I'm not sure I'd be the best person for it as I'm not intimately familiar with the otel format itself.

[bobstrecansky]

@atrauzzi - were you referring to this or were you referring to something else?

[atrauzzi]

Something like this: https://github.com/open-telemetry/opentelemetry-dotnet/blob/master/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md

[bobstrecansky]

I think it may be worth it to wait until the spec is hashed out to implement this. Thoughts?

[atrauzzi]

Definitely logic to that. Also gives this library a chance to settle on its API.

[bobstrecansky]

The OTEP maintainers are discussing this now: open-telemetry/opentelemetry-specification#699

[codeboten]

The OTLP exporter is now part of the spec: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/protocol/exporter.md

[bobstrecansky]

The specification for OTLP is found here

The specification for the exporter is found here

[bobstrecansky]

OTLP Trace Data format: https://github.com/open-telemetry/oteps/blob/master/text/trace/0059-otlp-trace-data-format.md

[bobstrecansky]

The HTTP version of this has been completed in #210

@riticksingh is now working on the gRPC implementation.

[bobstrecansky]

This has been completed by @SeanHood in #272