[connector/spanmetrics] Skip resource iteration in resetState when nothing needs resetting

[KimMJ]

Description

p.config.Histogram.Disable condition in resetState() function becomes stale from #32210 change. This makes p.config.Histogram.Disable condition as no-ops, cause m.histograms.ClearExemplars() is called only when p.config.Exemplars.Enabled && !p.config.Histogram.Disable. So when histogram is enabled (default) and exemplar is disabled (default), early return is false and need to loop through resource cache even though iteration doesn't call clearing exemplar.

Link to tracking issue

N/A. Found small issue during investigation and create PR since it is small fix.

Testing

created minimal test case. confirmed it failed before change, passed after change.

before

$ go test -count=1 -run TestResetStateSkipsIterationWhenNothingToReset -v .
=== RUN   TestResetStateSkipsIterationWhenNothingToReset
    connector_test.go:1443:
                Error Trace:    /opentelemetry-collector-contrib/connector/spanmetricsconnector/connector_test.go:1443
                Error:          Should be zero, but was 1
                Test:           TestResetStateSkipsIterationWhenNothingToReset
--- FAIL: TestResetStateSkipsIterationWhenNothingToReset (0.00s)
FAIL
FAIL    github.com/open-telemetry/opentelemetry-collector-contrib/connector/spanmetricsconnector        1.835s
FAIL

after

$ go test -count=1 -run TestResetStateSkipsIterationWhenNothingToReset -v .
=== RUN   TestResetStateSkipsIterationWhenNothingToReset
--- PASS: TestResetStateSkipsIterationWhenNothingToReset (0.00s)
PASS
ok      github.com/open-telemetry/opentelemetry-collector-contrib/connector/spanmetricsconnector        2.387s

Documentation

No update.

Authorship

• I, a human, wrote this pull request description myself.

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib.

Important reminders:

• Read our Contributing Guidelines.
• Sign the CLA if you haven't already.
• Follow the OpenTelemetry Generative AI policy: disclose any AI use in your contribution, and communicate (PR descriptions, review replies) in your own words rather than AI-generated text.
• Give reviewers at least a few days before pinging them for feedback.
• If you need help with general setup, development process, or contributor etiquette, ask in #opentelemetry-new-contributors.
• First-time contributors should keep at most one PR marked as ready for review until their first PR is merged; once two are open for review, any further PR is automatically converted to draft.
• If your change isn't one of our priority components, reviews may take more time.
• Raise technical or Collector-specific questions in #otel-collector-dev or a Collector SIG meeting.

[singhvibhanshu]

/workflow-approve

[KimMJ]

/rerun

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-09-12 04:39 UTC

Review the latest changes.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.