Mateusz "mat" Rumian

So I was thinking about creation of specific builder for YAML configs. Current implementation is very sensitive for any kind of human mistakes like whitespaces or invalid/not supported keywords. I...

@tigrannajaryan I think each receiver and exporter config should be little bit tuned - e.g. [zipkin-receiver](https://github.com/open-telemetry/opentelemetry-collector/blob/master/testbed/testbed/receivers.go#L234) - some kind of struct should be used there instead of raw text. I...

@dashpole I would like to share my opinion. What do you think about configuring additional env var holding resource attributes related to k8s in separated var like: ```yaml - name:...

@tybalex please set for Python instrumentation different exporter endpoint as Python instrumentation is using [OTLP HTTP exporter by default](https://github.com/open-telemetry/opentelemetry-operator/blob/main/pkg/instrumentation/python.go#L60). Please use eg. `http://collector-hostname:4318`. You can set it only for Python...

@pavolloffay based on that https://github.com/open-telemetry/opentelemetry-specification/issues/1885#issuecomment-934435972 I think we should set our instrumentations exporters to OTLP HTTP protocol.

@pavolloffay @akayaz What I found in the `gcr.io/bank-of-anthos-ci/frontend:v0.5.4` repository is that it already contains OpenTelemetry packages, please see [requirements.txt](https://github.com/GoogleCloudPlatform/bank-of-anthos/blob/v0.5.4/src/frontend/requirements.txt). I think there could be some dependency mix between Operator dependencies...

Hello Everyone, first of all I'm sorry for late response. I found that `metrics` are not supported by `otlp_proto_http` exporter. Only `gRPC` exporter supports both `traces` and `metrics`. I'm not...

> Do you have a link that explains the above for OTLP gRPC exporter? Or a link that lists what OS or python versions are supported? I've never seen anything...

I'm sorry I couldn't find a time to solve that on time. Closing as outdated (newer instrumentation already supported).

I think some documentation update would help to make this annotation visible to the community :)