Restore prometheus remote write exporter

[codeboten]

This issue tracks the work to restore the prometheus remote write exporter. It is a follow up to issue open-telemetry/opentelemetry-python#2291 which restores the prometheus exporter in the core repo.

[Doron-Bargo]

Hi @codeboten any update on restoring the Prometheus remote write exporter?
I notice it exists under metrics branch but never pushed to the main.

[vasireddy99]

Looks like we now have Prometheus exporter in the main branch.

[lzchen]

@vasireddy99

The current prometheus exporter that you are linking to is the pull-based prometheus exporter. We have yet to implement the remote-write exporter in the main branch using the updated metrics api/sdks.

[codeboten]

The current exporter that @vasireddy99 linked is the pull based exporter, @Doron-Bargo no one has taken on the work to bring back the remote write exporter. Would love help here if anyone has time for it

[haarakdy]

@codeboten what is the difference between prometheus remote write exporter and the exporter I use currently 0.17b0 ?
The exporter I use, the class PrometheusRemoteWriteMetricsExporter, pushes the data to the Logz.io and relies on gRPC.
Will this issue address #1142 performance depends on the amount of unique (label, value) tuples ?

[srikanthccv]

What you are using is based on the old API&SDK design which is no longer supported. There have been some significant changes since then and this issue is to restore the exporter to make it work with new API.

[Seefooo]

I think I can do this one. Going to take me a bit of time though as its my first OS contribution