otel scraper error metrics broken for splunkenterprise receiver

[kkburr]

The purpose and use-cases of the new component

My team needs an error metric in order to build an alert that tells us when our receiver is not healthy

Example configuration for the component

This new metric is not enabled by default, so if a team wants to use it they will have to add it to their configuration.

Telemetry data types supported

metrics

Code Owner(s)

me (Kaitlin Barrer)

Sponsor (optional)

No response

Additional context

In splunketnerprisereceiver, if the scrape method has any errors on any of its scrape targets, it returns a combined error. We would expect to see otelcol_scraper_errored_metric_points increment when this happens (defined in the main opentelemetry-collector repo here, but it's not, making errors difficult to detect.

[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. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.