Tyler Helmuth
Tyler Helmuth
Another related issue: https://github.com/open-telemetry/opentelemetry-operator/issues/1684
@aabmass what did you have in mind for setting the port to `4318`? If the user set `spec.exporter.endpoint` to any value with `4317` in it would we replace it with...
@pavolloffay @edeNFed @frzifus now that [donation is complete](https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/2) is this PR ready to be discussed?
/cc @nicolastakashi
I can't pretend to know the pain any language sigs are feeling from this restriction, but I want to caution us from making a decision based on our languages implementations...
> then they are already handling duplicate keys Depends on what you mean by handling. True support of duplicate keys feature would mean allowing both instances of the key to...
@halleystar are you saying that data exported by the `otlphttpexporter` have no resource attributes or that the metrics emitted by the otlphttpexporter don't have resource attributes?
Please add the debugexporter with `verbosity: detailed` and check in the collector logs if you have resource attributes.
Regardless of the `Start` interface we decide on, I think we 100% should be logging any of the Error statuses. In your alternative approach I like it keeps things unambiguous....
In my mind the blockers for this idea are then: 1. Are we ok with that edge case? 2. Should the behavior be configurable - should the user be able...