faro-web-sdk
faro-web-sdk copied to clipboard
OtlpHttpTransport: Revisit if correct sematic conventions are use, introduce Schema URL
Why
The OtlpHttpTransport package is in an early, experimental state. On of the reasons for that is that (some) semantic conventions for RUM and Browser were missing when the OtlpHttpTransport package was introduced.
- Let's double check if any new conventions are available which we are missing—easy to add, non-breaking
- Do we need / want to upgrade any attributes, e. g. are their any replacements for some
faro.*custom attributes—breaking -> vent if it the package is experimental, how can we ensure backwards compatibility or mitigate issues as much as possible? - Introduce schema/schema url (see: https://opentelemetry.io/docs/specs/otel/schemas/)
Not sure if it applies to what this issue is about but the opentelemetry convention for http has changed drastically recently. The changes can be seen in [this migration guide ](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/migration-guide.md