New component: DaprExporter and DaprReceiver

[pepperkick]

The purpose and use-cases of the new component

Utilize Dapr to send and receive OTEL signals to/from various Pub/Sub components that it supports.
https://docs.dapr.io/reference/components-reference/supported-pubsub/

It also abstracts the Pub/Sub configuration from collector utilizing the Dapr configuration.
https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-apache-kafka/

In Kubernetes, Dapr runs as sidecar with the collector container which exposes REST and gRPC API. Exporter can call those APIs to send the signals. Similarly Receiver can expose certain APIs for Dapr to call when an event is received from a subscribed topic.

Based on my knowledge, Dapr currently supports JSON format during transmission. So it may only support otlp_json format similar to PulsarReciever and PulsarExporter.

Example configuration for the component

receivers:
  dapr:
    # TBD

exporters:
  dapr:
    # TBD

Telemetry data types supported

traces
logs
metrics

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

No response

Sponsor (optional)

No response

Additional context

If this is okay with OTEL team then I can do a POC and work on these components.

[atoulme]

Is dapr here vendor specific? If so, would you be a representative of the vendor?

[pepperkick]

Not sure what exactly is considered vendor specific and I am not affiliated with Dapr if thatch the question. I am however using Dapr in my project.

Dapr is an open source tool that has many features, mainly it abstracts the messaging layer of an application which allows the PubSub provider to easily switched, like from Kafka to Pulsar without any change on application side.
https://github.com/dapr/dapr

[atoulme]

OK, let's assume it's not vendor specific for now.

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

[github-actions]

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