-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[opentelemetry-php-contrib] SdkBundle: OTLP exporter factory creates exporter with default values #1146
Comments
I have same issue. URL for configuration always taking from You have to look at https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md |
Workaround if you only require a simple setup (one processor, one exporter, etc.):
e.g. if you want to use OpenTelemetry\API\Trace\TracerProviderInterface:
synthetic: true and then somewhere appropriate in your Kernel you just inject it into the container: protected function initializeContainer(): void
{
parent::initializeContainer();
/**
* @psalm-suppress MixedMethodCall
*/
$this->container->set("OpenTelemetry\API\Trace\TracerProviderInterface", Globals::tracerProvider());
} |
Describe your environment Describe any aspect of your environment relevant to the problem, including your php version (
php -v
will tell you your current version), version numbers of installed dependencies, information about your cloud hosting provider, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on master.Tried on both
and
Steps to reproduce
With the config:
The OTLP span exporters are created with default values for
protocol
andendpoint
instead of the values defined in the config.I guess the SdkBundle is not setting the values in the config the factory is trying to access.
What is the expected behavior?
Exporters configured as I specified
What is the actual behavior?
Exporters configured with default values
The text was updated successfully, but these errors were encountered: