[receiver/collectd] Refactor Observability.go from opencensus to pdata

[ZenoCC-Peng]

Component(s)

receiver/collectd

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

Hi,
I hope someone can refactor collectdreceiver/observability.go.
It appears that certain sections of the code still rely on opencensus.

import (
	"context"

	"go.opencensus.io/stats"
	"go.opencensus.io/stats/view"
)

Furthermore, I've noticed that there are other collectors that also employ similar logic for handling observability.go (ex: k8sattributesprocessor).

Describe the solution you'd like

Hope people can reactor part of observability.go to pdata.

Describe alternatives you've considered

No response

Additional context

From what I know, the purpose of this code is to record events of success and failure.

I've seen someone use module obsreport in opentelemetry-collector-contrib to achieve similar functionality, For example, in the splunkhecreceiver.

However, the metric mode in obsreport refers to "go.opentelemetry.io/otel/metric," which refers from https://pkg.go.dev/go.opentelemetry.io/otel/metric and it's different from "pmetric".

[github-actions]

Pinging code owners:

• receiver/collectd: @atoulme

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/collectd: @atoulme

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