Robert Pająk

@ArthurSens, are you going to also work on prototype for [prometheusreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/prometheusreceiver)?

Given https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/40004#issue-3057707170: > Turns out our exporter never exposed otel_scope_info, so this PR just introduces the addition of the new labels. and https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/3c6a5ea6430afaac7c33a25ff276903ef829693b/receiver/prometheusreceiver#resource-and-scope: > It drops the `otel_scope_info` metric, and...

I created a specification PR. PTAL: - https://github.com/open-telemetry/opentelemetry-specification/pull/4505

This issue is still valid.

Shouldn't https://github.com/splunk/public-o11y-docs/blob/main/_includes/requirements/python.rst be also updated?

Can you add a changelog entry?

_I shared it also via a different channel, but I think it may be good if I also leave some comment here._ It looks like problems are not caused by...

@julianocosta89, has the `GOMEMLIMIT` been set also to k8s setup? I see only a PR for docker.

> Why? Description updated. Thanks

> There's no corresponding SDK behavior that would allow the enabled API to change its response based on context. A custom API implementation (e.g. SDK wrapper) could change its response...