httpcheck reciever - custom attributes in the reciever config

[mabac16]

Component(s)

receiver/httpcheck

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

hi, there is a need to also via this receiver be able to set a custom attribute in the reciever and not just processor.
Example

httpcheck/test:
    metrics:
      httpcheck.tls.cert_remaining:
        enabled: true
    targets:
      - method: GET
        endpoints:
          - "xxxx"
        attributes:
          customkey: customvalue

thanks for looking at this.

Describe the solution you'd like

be able to set a custom attribute in the receiver and not just a processor like:

        attributes:
          customkey: customvalue

Describe alternatives you've considered

using processors but do to implementation this will create more and unwanted complexity.

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners:

• receiver/httpcheck: @codeboten @VenuEmmadi

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

[VihasMakwana]

@mabac16 Can you please give an concrete example of this use case and why do you need this?

Do you want the receiver to set the attributes on the telemetry data it exports to the processor/exporter?

[mabac16]

hi @VihasMakwana, Sure !
Instead of writing logic in a processor it would be easier to have the option to maintain it in the receiver. We are building our config dynamically using ansible and jinja2 and would like to avoid adding processors and logic around it.
the older signalfx/splunk smartagent/http receiver has this option e.g:

extraDimensions:
      monitor: kafka_connect_health

the filelog reciever also has this option for example.

so yes, id like to have the option in the httpcheck reciever as well for simplicity, less maintenance reasons.

[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/httpcheckreceiver: @codeboten @VenuEmmadi

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

[mabac16]

pinging @codeboten @VenuEmmadi