[exporter/googlecloud]: Timeout doesn't seem to be respected for logs

[BinaryFissionGames]

Component(s)

exporter/googlecloud

What happened?

The timeout parameter doesn't seem to matter for sending logs. I think it's entirely ignored.

You can see in the factory that the timeout is passed to the constructor function for the traces/metrics exporter, but the logs exporter does not get the timeout:

opentelemetry-collector-contrib/exporter/googlecloudexporter/factory.go

Line 58 in 1b03346

logsExporter, err := collector.NewGoogleCloudLogsExporter(ctx, eCfg.Config, params.TelemetrySettings.Logger, params.BuildInfo.Version)

Collector version

v0.108.0

Environment information

No response

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/googlecloud: @aabmass @dashpole @jsuereth @punya @damemi @psx95

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[dashpole]

@damemi can you take a look at this if you have time?

[damemi]

cc @braydonk do you know if there's a specific reason not to have the timeout passed to the logging exporter? Or could we just add that?

[braydonk]

@damemi Just looks like an oversight to me. Should be able to pass in a timeout to the logs exporter and then use that when creating contexts for the loggingClient calls, similar to how it's done in the metric and trace exporters.

[damemi]

This will be included in the next release of our exporter with GoogleCloudPlatform/opentelemetry-operations-go#894 merged