winperfcounters receiver reports no metrics if any scraper fails

[chrislbs]

Component(s)

receiver/windowsperfcounters

What happened?

Description

In the windows perf counter receiver, if any instance or object fails to receive, all metrics are thrown away rather than just the scrapers that failed to successfully read.

Steps to Reproduce

Create a windowsperfcounter receiver for an instance that exists, and another that doesn't.

Expected Result

Metrics will be received and exported for the perf counter instance that exists.

Actual Result

Metrics are not received or exported for the perf counter instance that exists.

Collector version

v0.66.0

Environment information

No response

OpenTelemetry Collector configuration

receivers:
  windowsperfcounters:
    metrics:
      dotnet.gen0.heap.size:
        description: dotnet gen 0 heap size
        unit: By
        gauge:
    collection_interval: 30s
    perfcounters:
    - object: .NET CLR Memory
      instance:
      - "notexist.exe"
      - "exists.exe"
      counters:
        - name: "Gen 0 heap size"
          metric: dotnet.gen0.heap.size

service:
  pipelines:
    metrics:
      receivers: [windowsperfcounters]

Log output

No response

Additional context

No response

[chrislbs]

/label receiver/windowsperfcountersreceiver

[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/windowsperfcounters: @dashpole

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/windowsperfcounters: @dashpole

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

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.