Proposal: Extend Logs Bridge API instead of creating separate Events API

[pellared]

Would it not make sense to make the Logs (Bridge) API useable for creating events?

The Events API has only one additional parameter which is the "event name".

Couldn't we add EventName to the Bridge API's Emit Record and just call out the differences in the API implementation when it is set?

EDIT: I see that this is a counter-issue for #3086.

[pellared]

Never mind. I think that it makes sense to have it as a separate API because it serves a different use-case and the APIs may evolve orthogonally.

Unlike the Logs Bridge API, application developers and instrumentation authors are encouraged to call this API directly.

At first glance it looks suspicious as the APIs look almost identical.