Arthur Silva Sens

PoC for Prometheus exporter in collector-contrib: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/40004 Reviews appreciated, especially in test coverage of edge cases :)

> @ArthurSens, are you going to also work on prototype for [prometheusreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/prometheusreceiver)? I spent some time yesterday and it was not as easy as I expected, but I'm also not...

PoCs in collector are ready for review: * https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/40060 * https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/40004

> Maybe this could be bundled up with the idea of one binary for both prometheus and promtool. The "mode" of the binary could be selected with a command line...

Not sure why this wasn't closed by #14747 🤔, closing now

I'm a bit concerned about "metrics highjacking", where someone could steal metrics from a Prometheus instance by deploying a RemoteWrite CRD. I don't mean to mention this as a blocker,...

> This would be a breaking change for anyone relying on the exact values, but overall a benefit. I'm curious how we handle such situations... With no data other than...

> I've seen alerts built on top of a particular bucket for things like HTTP request durations, but never for go metrics. Actually, with this same line of thought, does...

I'm in favor, making sure we do some good communication around this change

Sorry, I don't mean to block the work here 😬 I remember that during the office hours, I mentioned that the UX for the proposed solution still feels a bit...