When using the ReplayFIle option in the otlpjsonfilereceiver, we get spammy logs

[ridwanmsharif]

Component(s)

pkg/stanza/fileconsumer

Is your feature request related to a problem? Please describe.

Specifically this log:

opentelemetry-collector-contrib/receiver/otlpjsonfilereceiver/file.go

Line 44 in 26dd5a6

ReplayFile bool `mapstructure:"replay_file"`

Describe the solution you'd like

I believe this is happening because when the ReplayFile option is used, the fileconsumer uses the noStateTracker file tracker:

opentelemetry-collector-contrib/pkg/stanza/fileconsumer/internal/tracker/tracker.go

Line 143 in 26dd5a6

type noStateTracker struct {

And this results in a new reader created each time a scrape is done:

opentelemetry-collector-contrib/pkg/stanza/fileconsumer/file.go

Line 266 in 26dd5a6

r, err := m.readerFactory.NewReader(file, fp)

To fix this, maybe we check for the tracker here before logging this log line.

Describe alternatives you've considered

Alternative 1: Remove this log line
Alternative 2: Allow the otlpjsonfilereceiver mute some errors

Additional context

No response

[github-actions]

Pinging code owners:

• pkg/stanza/fileconsumer: @djaglowski @andrzej-stencel

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

[ridwanmsharif]

I'll send a PR with my suggestion: skip this log line if the noStateTracker is being used

I'm curious if there are other ideas though - muting certain errors seems like a useful ability across many components