New component: `httpclientreceiver`

[verejoel]

The purpose and use-cases of the new component

This would pretty much do the same thing as Vector's HTTP Client source.

For us an immediate use-case would be scraping Alertmanager API and emitting these data as logs on some regular interval.

Example configuration for the component

httpclient:
  endpoint: http://example.com
  method: GET
  headers:
    Content-Type: application/json
  interval: 1m
  decoder: json

Telemetry data types supported

Data would be emitted as logs, I don't really see a way metrics or traces could be supported.

Code Owner(s)

@verejoel

Sponsor (optional)

@atoulme

Additional context

We're trying to implement the pipeline detailed in https://blog.cloudflare.com/alerts-observability/ with OTel instead of Vector.

[atoulme]

I can sponsor this component. I expect it will have quite a few design decisions coming with it, and I'd encourage that we reuse the encoding extensions to handle incoming payloads for it.

I agree only logs make sense, and we can process and use connectors to transform logs into metrics if need be.

[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.