[receiver/splunkenterprise] Add initial_delay top-level Configuration

[michael-burt]

Component(s)

receiver/splunkenterprise

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

If a user rotates credentials on a Splunk Enterprise host and restarts OpenTelemetry Collector at the same time, the Splunk credentials will often lock out because the new credentials in use by Otel are not yet active in Splunk.

Describe the solution you'd like

Just like in the HTTP Check Receiver, I would like to see a configuration for initial_delay so that the Splunk Enterprise Receiver waits a pre-defined amount of time before initiating scrapes. This will allow time for the credentials to become active in Splunk.

Describe alternatives you've considered

Alternatives include waiting to start the collector. Downsides to this approach are that the entire collector is unavailable during this "warm up" time. Adding an initial_delay would allow other components to operate.

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername

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

[VihasMakwana]

Sounds like a valid request. Let's see what codeowners has to say about it.

[jherbage]

I think this can be closed.
We didn't realise that initial_delay is configured as an option on all receivers using the scraperhelper as splunkenterprisereceiver is.