Make buildevents more generic by using OpenTelemetry instead of beeline lib.

[ringods]

Is your feature request related to a problem? Please describe.

No.

Describe the solution you'd like

The buildevents library is very handy to get insight into a CI system, but the current implementation is limited to Honeycomb.io because it builds against the Honeycomb beeline library. If we would switch to use the Opentelemetry Go SDK, output could be collected on anything supporting the OpenTelemetry Collector, still including Honeycomb.io.

Describe alternatives you've considered

Searched for alternatives, but haven't found anything which came as close to buildevents

Additional context

[MikeGoldsmith]

Hey @ringods - thanks for the feature request. We'll add it to our backlog for prioritisation.

[kentquirk]

Thank you for the suggestion. Because this project is so specific to the use case, we think that OTel is not really a good match for its needs. There are specific things it does using Honeycomb's native events (the watch command for CircleCI, for example) that would be difficult to replicate in a generic OTel solution. Just letting you know that it's not likely to rise out of the icebox soon.

[dmathieu]

I think rather than using the otel library directly, what would be nice here is if buildevents would support OTLP.
Then it would still be able to start/finish traces its own way. But could send them to any OTLP-valid provider, or OpenTelemetry Collector.