New component: Faro Receiver

[rlankfo]

The purpose and use-cases of the new component

The purpose of this component would be to ingest telemetry data sent from Grafana Faro.

Example configuration for the component

receivers:
  faro:
    http:
  faro/withcors:
    http:
      cors:
        allowed_origins:
          - *

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 proposing to contribute this as a representative of the vendor.

Sponsor (optional)

@jpkrohling @kovrus

Additional context

The Grafana Faro Web SDK is a highly configurable open source JavaScript agent that can easily be embedded in web applications to collect real user monitoring (RUM) data: performance metrics, logs, exceptions, events, and traces.

[jpkrohling]

I'm sponsoring this.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[NickLarsenNZ]

Hopefully the stale label can be removed soon. I came here searching for this feature (as I already use the otel collector for backend apps).

[chriskuchin]

What is the status here? Would love to use this as we are using the Otel Collector already. Noticed the PR above seems to be abandoned.

[clbrec]

@rlankfo any updates here? I'm also interested in this as faro looks pretty promising!

[rlankfo]

@NickLarsenNZ @chriskuchin @clbrec thanks for inquiring here; I'm glad to see there is interest in using Faro!

While the changes in my PR linked on this issue mostly worked, there were some conceptual issues I wasn't sure how to get around. This is because Faro payloads get split into multiple signals (logs, traces) and I couldn't seem to implement this cleanly. I brought this up with @jpkrohling and I believe he's taken it to the collector SIG for discussion.

In the mean time, I plan to add a Faro translator which can be used in the receiver. Once there is some clarity around how a receiver should output multiple signals then this work should proceed. I'm sorry that I'm not sure what the timeline is here but hopefully sooner than later 🤞

[JalisDiehl]

Hey Guys, for us it`s quite interesting use otel with Faro, if you need any help even with docs, please contact me... Our Engineering team might help you

[srinivasmummareddy]

@rlankfo Is there any update on this? We are really interested in using this receiver

[alexlionnel]

I am really interested in using faro receiver. Any update on this?

[jpkrohling]

There has been no progress, I'm afraid.

[rlankfo]

Hi all, sorry for the delays. We've had some internal discussions on the best way to move forward on this and hoping to get the work slated over the next quarter or two.

In the meantime, the faro-web-sdk does offer an experimental otlp http transport that may be worth looking into: https://github.com/grafana/faro-web-sdk/tree/main/experimental/transport-otlp-http

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[rlankfo]

I believe this is still a relevant issue as several community members and otel users have expressed interest.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[mar4uk]

it is still relevant

[mar4uk]

Hey! We need a sponsor for this component. Would anyone like to sponsor it?

[ceastman-r7]

Still relevant and needed.