New component: Faro exporter

[mar4uk]

The purpose and use-cases of the new component

The purpose of this component would be to export telemetry in Faro format

Example configuration for the component

exporters:
  faro:
    endpoint: https://example-endpoint.com/collect/app-key-example

Telemetry data types supported

Logs
Traces

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

mar4uk, rlankfo

Sponsor (optional)

No response

Additional context

No response

[atoulme]

Reviewed quickly during the SIG meeting on 9/24: this is not a vendor-specific component if it targets an open source solution in my opinion.
@jpkrohling would you please review?

[mar4uk]

Hey @atoulme! Thank you for reviewing! Faro exporter is a vendor-specific (Grafana) component because the target is the Faro collector whose code is not an open source

[atoulme]

Understood. @mar4uk, we have some new rules where we try to limit vendor-specific to one per type (exporter, processor, receiver, connector). See https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#vendor-specific-components

This might mean this component would be called "grafanaexporter", exporting to Faro.

[mar4uk]

Thank you for clarifications! Got it. Currently, there are no grafana-specific exporters in the repo, which means rules are not violated. I will name it grafanaexporter as you proposed 👍

[mar4uk]

After a discussion with the team, decided to contribute this component as vendor-neutral component.
The purpose of this component would be to export data in Faro format. So anyone can use any backend to store faro data.

Having Faro receiver, Faro exporter components will allow receive Faro data from faro-web-sdk, process it, and export to any backend in Faro format