otel-col error messages while openseach is not reacheable

[julianocosta89]

Bug Report

Which version of the demo you are using?
395f385

Symptom

When starting the demo, opensearch takes a couple of seconds to start. Meanwhile the Collector keeps trying to send logs to it, resulting in a bunch of error messages like this one:

2024-09-23T07:25:51.299Z	error	exporterhelper/common.go:296	Exporting failed. Rejecting data.	{"kind": "exporter", "data_type": "logs", "name": "opensearch", "error": "not retryable error: Permanent error: Permanent error: flush: dial tcp 172.21.0.3:9200: connect: connection refused\nPermanent error: Permanent error: flush: dial tcp 172.21.0.3:9200: connect: connection refused", "rejected_items": 127}
go.opentelemetry.io/collector/exporter/exporterhelper.(*baseExporter).send
	go.opentelemetry.io/collector/[email protected]/exporterhelper/common.go:296
go.opentelemetry.io/collector/exporter/exporterhelper.NewLogsRequestExporter.func1
	go.opentelemetry.io/collector/[email protected]/exporterhelper/logs.go:134
go.opentelemetry.io/collector/consumer.ConsumeLogsFunc.ConsumeLogs
	go.opentelemetry.io/collector/[email protected]/logs.go:26
go.opentelemetry.io/collector/internal/fanoutconsumer.(*logsConsumer).ConsumeLogs
	go.opentelemetry.io/[email protected]/internal/fanoutconsumer/logs.go:64
go.opentelemetry.io/collector/processor/batchprocessor.(*batchLogs).export
	go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:496
go.opentelemetry.io/collector/processor/batchprocessor.(*shard).sendItems
	go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:261
go.opentelemetry.io/collector/processor/batchprocessor.(*shard).startLoop
	go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:223

What is the expected behavior?

I expect to see no errors on the collector logs, except when there is an actual error.

Reproduce

docker compose up -d
docker logs otel-col