[receiver/filelog]: Log glob IO errors

[BinaryFissionGames]

Component(s)

receiver/filelog

Describe the issue you're reporting

Currently, we are globbing and ignoring any IO errors, which is the default behavior of the glob library we are using. However, this means that any errors that are gotten here are swallowed silently by the receiver.

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/c15794f8b3ad8bdf1bbf5abfba8486df4ad1b7c9/pkg/stanza/fileconsumer/finder.go#L21C2-L21C2

Instead, I think it would be ideal if we used the WithFailOnIOErrors option (https://pkg.go.dev/github.com/bmatcuk/doublestar/v4#WithFailOnIOErrors) initially, and if fails, log a warning (or maybe even just a debug level log?), and fall back to using the current behavior.

This would help to debug instances where globbing is actually failing (can't access dir because of permissions, for instance), and silently leads to files not being picked up by the receiver.

[github-actions]

Pinging code owners:

• receiver/filelog: @djaglowski

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

[djaglowski]

@BinaryFissionGames, makes sense to me. Should I assign this to you?

[BinaryFissionGames]

@djaglowski Yes, please do. Thanks!

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/filelog: @djaglowski

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

[djaglowski]

@BinaryFissionGames, are you still planning to work on this?