Arthur Silva Sens

It could work if we add a CI check to block if there's no changelog entry. In prometheus it's already super clunky because PRs more often don't include that entry...

Before adding such thing, I think we'll need to revisit how we organize our documentation (that's why we added the project idea to GSoC). If we're adding graphs, I think...

Not stale, we're still waiting for a client_golang release

urgh, I'm having a harder time than I'd like to admit with #1389, which is blocking this PR

@jmichalek132 as discussed in a few calls this week, let me take over this PR so you can focus on your mentorship project :) @aknuds1 @ywwg, I'm wondering what we...

> I think the PR needs to define properly which problem is being solved. Jumping into a solution isn't the best approach. Yes exactly! I was hoping we could come...

> Agree, we need to decide on a solution to the problem laid out in [OpenTelemetry → Prometheus: type+unit suffixes](https://docs.google.com/document/d/1t4ARkyOoI4lLNdKb0ixbUz7k7Mv_eCiq7sRKHAGZ9vg/edit#heading=h.4mz5gmed52o5), right? > > The agreed upon solution would have to...

If the team decides that we really want to wait for proper unit/type handling, I guess I could continue the PR... just changing the default to `ClassicPrometheusTranslation`

> > After the inperson meeting Goutham realized that it’s not as easy as initially thought. We need to account for metric name collision if we don’t handle unit and...

I've updated the PR to not translate UTF8 characters by default. I'm also not touching unit/type suffixes in any way! I'm happy to change the PR again to allow not...