New component: prometheus remotewrite receiver

[adamkubon]

The purpose and use-cases of the new component

It consumes data from prometheus remote-write protocol

Example configuration for the component

receivers:
  prometheusremotewrite:
    endpoint: 0.0.0.0:19291

Telemetry data types supported

metrics

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)

No response

Additional context

There are existing prometheus receivers, but no any remote-write interface support

[kovrus]

Hi @adamkubon, here is already an issue for that #10358.

cc: @jpkrohling

edit: ah, actually I see that you have done some work already #14752

[jpkrohling]

I'm closing this issue in favor of #10358, but the PR can be kept.

[jpkrohling]

I'm reopening this, closing #10358, as this fits better as a proposal for a new component, while that has served its purpose as a place to have some discussions on the idea for this component.

[jpkrohling]

I believe @kovrus is going to volunteer for working on this soon, if he hasn't already. He'll be the code owner, and I'm a sponsor for this.

[kovrus]

Heads up: I've put together a short design doc that covers the current state of Prometheus rw, implementation issues, and possible implementation approaches. It seems that the implementation of this component would require some changes to rw.

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

[disfluxly]

Hey everyone - curious if there's any update on this? This would be very beneficial to have on quite a few fronts!

[hughesjj]

Hey @disfluxly , I'm personally prototyping something for my own company and will be bringing up our learnings come April 26th @8AM PDT in the next prometheus working group meeting (barring any unforeseen battles I might get pulled into last minute)

All are welcome to join!

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

[punya]

Heads up: I've put together a short design doc that covers the current state of Prometheus rw, implementation issues, and possible implementation approaches. It seems that the implementation of this component would require some changes to rw.

I can't access the linked design doc - any chance you could make it more broadly visible? Thanks!

[jpkrohling]

There were some changes in how files are shared externally and this doc predates that. I'm working on getting this file shareable externally again. If I don't get back to you in a day or two, ping me again!

[jpkrohling]

@punya, can you try again? It should be public now.

[disfluxly]

Curious if there's been any movement here? Last comments on the Design Doc seem to be from April.

[jpkrohling]

Unfortunately, it's not in our queue anymore. If you are willing to help, feel free to pick it up.

[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 closed as inactive because it has been stale for 120 days with no activity.