Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New component: Faro Receiver #19180

Open
2 tasks
rlankfo opened this issue Mar 3, 2023 · 18 comments
Open
2 tasks

New component: Faro Receiver #19180

rlankfo opened this issue Mar 3, 2023 · 18 comments
Labels
Sponsor Needed New component seeking sponsor

Comments

@rlankfo
Copy link
Contributor

rlankfo commented Mar 3, 2023

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.

@rlankfo rlankfo added the needs triage New item requiring triage label Mar 3, 2023
@jpkrohling jpkrohling added Accepted Component New component has been sponsored and removed needs triage New item requiring triage labels Mar 3, 2023
@jpkrohling
Copy link
Member

I'm sponsoring this.

@github-actions
Copy link
Contributor

github-actions bot commented May 2, 2023

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 github-actions bot added the Stale label May 2, 2023
@jpkrohling jpkrohling removed the Stale label May 11, 2023
@github-actions
Copy link
Contributor

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 github-actions bot added the Stale label Jul 11, 2023
@NickLarsenNZ
Copy link

NickLarsenNZ commented Aug 5, 2023

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).

@github-actions github-actions bot removed the Stale label Aug 6, 2023
@chriskuchin
Copy link

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
Copy link

clbrec commented Oct 10, 2023

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

@rlankfo
Copy link
Contributor Author

rlankfo commented Nov 1, 2023

@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
Copy link

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
Copy link

srinivasmummareddy commented Feb 13, 2024

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

@alexlionnel
Copy link

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

@jpkrohling
Copy link
Member

There has been no progress, I'm afraid.

@rlankfo
Copy link
Contributor Author

rlankfo commented Apr 30, 2024

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

Copy link
Contributor

github-actions bot commented Jul 1, 2024

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 github-actions bot added the Stale label Jul 1, 2024
@rlankfo
Copy link
Contributor Author

rlankfo commented Aug 1, 2024

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

@github-actions github-actions bot removed the Stale label Aug 2, 2024
Copy link
Contributor

github-actions bot commented Oct 2, 2024

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 github-actions bot added the Stale label Oct 2, 2024
@mar4uk
Copy link
Contributor

mar4uk commented Oct 2, 2024

it is still relevant

@github-actions github-actions bot removed the Stale label Oct 3, 2024
@jpkrohling jpkrohling added Sponsor Needed New component seeking sponsor and removed Accepted Component New component has been sponsored labels Nov 6, 2024
@mar4uk
Copy link
Contributor

mar4uk commented Nov 12, 2024

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

@ceastman-r7
Copy link

Still relevant and needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sponsor Needed New component seeking sponsor
Projects
None yet
Development

No branches or pull requests

10 participants