Federico Torres

I'll start by implementing UTF-8 support in the Java client library

@fstab You can find the proposals @ywwg worked on [here](https://github.com/prometheus/proposals/blob/main/proposals/2023-08-21-utf8.md) and [here](https://github.com/prometheus/proposals/blob/main/proposals/2023-11-13-utf8-migration.md). I'm working on adding UTF-8 metric and label name validations and support for parsing and formatting the UTF-8...

Thanks for the info @fstab! I don't think another proposal is necessary, but I appreciate the points you mentioned and will take them into account for the implementation.

Hello @fstab, I see that there's still some discussion going on about OpenTelemetry metric names conversion, but I think that the PR is ready for an initial review, at least...

Hey @fstab, I just wanted to check in regarding this PR. I understand there might still be ongoing talks about the OpenTelemetry metric names conversion, but I was wondering if...

The path for pushing metrics into the Pushgateway looks like `/metrics/job/{//}` Currently, job names and label values can be encoded with base64url, in which case `job` or the label name...

> is there content negotiation with calls to pushgateway, or do people just hit the endpoint? (What if someone sends either of these formats to an older endpoint that doesn't...

Yeah, I think the escaping alternative makes more sense. +1 on the opt-in. I'll start looking into it, thanks for the feedback!

@shashank-priyadarshi Thanks! I'm making progress on this already on my end

@beorn7 Thanks for your feedback, the requested changes were addressed.