You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
Telemetry data types supported
traces
logs
metrics
Is this a vendor-specific component?
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.
The text was updated successfully, but these errors were encountered: