[receiver/splunkenterprise] Configuration options for querying different enterprise instance types (SH, Indexer, Manager, etc)

[greatestusername]

Component(s)

receiver/splunkenterprise

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

Some metrics require querying specifically a Search Head or specifically an Indexer (or a cluster manager, etc). Config currently only allows one endpoint that is expected to point at an Indexer and currently produces primarily Indexer metrics.

While possible to setup multiple receiver instances pointing at various instance types that would also require manually enabling/disabling the correct metrics for that instance type.

Describe the solution you'd like

Have optional configuration fields for different types of splunk enterprise instances that would then enable the metrics for that type of instance when applied. Essentially have optional fields for something like indexer_endpoint, search_head_endpoint, cluster_manager_endpoint and have metrics related to these specific instance types only be enabled when their instance type endpoint is defined.

receivers:
    splunkenterprise:
        auth: basicauth/client
        indexer_endpoint: "https://21.1.1.1:8089"
        sh_endpoint: "https://31.1.1.1:8089"
        cluster_manager_endpoint: "https://11.1.1.1:8089"
        timeout: 45s

Describe alternatives you've considered

Possible to have multiple instances of the receiver, one for each type, but this is fiddly with enabling/disabling metrics.

Could allow a list of instances but would still require enabling/disabling metrics based on what instance types would be in the list

Additional context

Search head and cluster manager specific metrics will be added soon and this work would be a pre-requisite to adding those metrics.

[github-actions]

Pinging code owners for receiver/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Removing needs triage as this was filed by a code owner of the component, and it generally makes sense to me.

[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/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername

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

[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/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername

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

[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/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername

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