[simple prometheus receiver]Support customized job name in configuration

[chenlujjj]

Component(s)

receiver/simpleprometheus

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

Hi team, we use the simple prometheus receiver within the receiver creator to scrape metrics from k8s pods with specific annotations, the config is like:

receiver_creator/application:
      receivers:
        prometheus_simple/app_pods:
          rule: type == "port" && pod.annotations["prometheus.io/scrape"] == "true" && ( string(port) == pod.annotations["prometheus.io/port"] || name == pod.annotations["prometheus.io/port"] )
          config:
            endpoint: '`endpoint`'
            metrics_path: '`"prometheus.io/path" in pod.annotations ? pod.annotations["prometheus.io/path"] : "/metrics"`'
            collection_interval: '`"prometheus.io/collection_interval" in pod.annotations ? pod.annotations["prometheus.io/collection_interval"] : "30s"`'

it works good, but a small problem is that the simple prometheus receiver uses the prometheus_simple/$endpoint as the job name which would be transformed to service.name label in the metric.

It will be great if we can customize the job name here.

Describe the solution you'd like

Add a job name setting in the configuration. The setting is optional.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/simpleprometheus: @fatsheep9146

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

[fatsheep9146]

@chenlujjj Thanks for your advise, I will take a look at this.

[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/simpleprometheus: @fatsheep9146

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

[freshyjmp]

Also running into this. Would appreciate some other way to not have job_name always become service.name. For some applications deployed via operator they have multiple metric paths, but all metrics should be rolled up under one service.name

[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/simpleprometheus: @fatsheep9146

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

[jmichalek132]

not stale

[chenlujjj]

Hi @fatsheep9146 , have you got time to review the PR ?